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. There's two other options I was suggesting: 1. at the end before filing bugs, just resubmit all failed builds. This would allow for 'fixing' packages in the case that something that broke them in the buildroot had been fixed since or the failed due to some transitory infra problem. Not sure this is worth it unless we actually identify some widespread fix or see lots of infra problems. 2. More complex would be to rebuild a-z, then merge the side tag, then resubmit all the failed builds again. Further thought about this is that one round might not be worth it and more rounds would be more disruptive/complex. So in the end, I think what we are doing now is probibly the best fit for the current workflow... kevin
Attachment:
signature.asc
Description: PGP signature
-- _______________________________________________ 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
