On Wed, 2025-07-30 at 13:35 +0200, Michael J Gruber wrote: > Kevin Fenzi venit, vidit, dixit 2025-07-29 19:04:31: > > I think this is all too big a hammer. > > > > There's lots of cases where people make small changes and don't think > > it's worth doing a new build, but expect it will get picked up in the > > next one. > > > > So, perhaps a more targeted approach might work? Say a week before the > > mass rebuild, add a comment to all 'stuck in gating' rawhide updates > > saying 'hey, the mass rebuild is starting in a week, please fix this or > > the day before the mass rebuild we will unpush this and revert git to > > the previous passing builds commit' > > > > Thats yet more work for releng/qe, but some/much of it might be > > automatable. > > Taking this a bit further: > > Is there any valid reason to push a commit to rawhide dist-git without > building it?
Remember, it's not only about building. In this specific case that was the issue, but we also have several problems of the type 'package was built but failed gating, nobody fixed the test failures before the mass rebuild happened'. -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue