On Wed, 2019-11-06 at 17:10 -0500, Randy Barlow wrote:
On Wed, 2019-11-06 at 21:32 +0100, Miro HronĨok wrote:
> Is there any good way to get notified about this sort of problems in
> timely manner prior to the update being pushed? This is currently not
> optimal.
I'm not familiar with an existing solution to this problem, but I agree
that it is not optimal.
I had a chat or three with Brian Stinson about some ways we could deal
with problems like this. Today, when we CI packages (i.e., Bodhi
gating), we typically just run the tests associated with the package
being altered. Brian suggested that we could *also* run the tests of
the packages that depend on the package being altered, against the
altered package. This way if a change to something (like pyramid) would
break a dependent package's tests (such as cornice), then the update
for pyramid should get a failed test result on its tests tab.
Something like this
would be also very very useful for the Anaconda installer &
helthy compose flow. Many failed composes and installation problems are often
not issues in Anaconda itself, but the many tools and libraries it interacts
with changing behavior and breaking the installer & compose generation.
If new build of these components triggered the Anaconda test suite, lot of this
breakage could be averted and fixed early on before actually affecting anyone.
The
problem is that this does increase the load on the test system greatly,
but perhaps we can get enough hardware to make that OK. Not sure.
_______________________________________________
devel mailing list -- devel(a)lists.fedoraproject.org
To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org