On Sun, Jan 19, 2025 at 09:10:52AM -0800, Kevin Fenzi wrote: > On Sun, Jan 19, 2025 at 03:36:32PM +0000, Zbigniew Jędrzejewski-Szmek wrote: > > On Sat, Jan 18, 2025 at 10:04:28AM -0800, Kevin Fenzi wrote: > > > > The only way that works, is what mockchain does: build the packages in > > > > random order. if any fails, repeat while at least one package in the loop > > > > succeed. > > > > > > So, this is an interesting idea. Perhaps we should start doing this for > > > mass rebuilds? It should be pretty easy to wait for it to finish, gather > > > all the failed ones and resubmit them, see if any worked, if so, > > > resubmit again. This would of course make things take longer and would > > > be a waste of cpu/etc, and it would generate more notification noise to > > > maintainers, but it might save work in the end? Most of the failing > > > packages would likely fail pretty fast too. > > > > Isn't this what is hapenning already? We can categorize the current > > alphabetical order as (one of the possibilities of pseudo-) random order. > > Right now we rebuild each package a-z and then are done and merge the > side tag and file bugs on everything that failed. Oh, I was under the impression that the mass rebuild retries the failed builds in a loop. I had a different mental model of what happens. But since the builds are independent, then this does make sense to just try once. So… what's the quidance for packages that failed in the mass rebuild: - commit fixes to dist-git and push - commit fixes to dist-git and push and build normally - commit fixes to dist-git and push and build into f42-build - wait until the mass rebuild is done and only then push fixes ?? Zbyszek -- _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
