On Tue, 25 Jan 2022 at 19:13, Kevin Fenzi <kevin@xxxxxxxxx> wrote: > > Greetings. > > The mass rebuild finished it's first pass on saturday morning, leaving > 3448 failed builds. > > We then did a second pass yesterday ( 2022-01-24 ) of all failed builds, > and that resulted in 1282 failed builds. > > The f36-rebuild tag is being merged now, but unfortunately our SOP had > it merge via f36-signing-pending, so all the builds will pass through > signing again, which will be a slow process. We have updated docs and > next time will be just tagging directly into the final tag and signing > along the way. > > There's a gcc build currently going that has fixes for some common > issues that caused failures on ppc64le builds along with some other > fixes. As soon as it's done we are going to do another pass of > resubmitting the failed builds and will tag any that finish there. > > After that we will be done and it will be on maintainers to sort out > FTBFS issues. What do we do with the FTBFS issues filed as a result of the ppc64le issues? Do we close them, or are they gonna be closed automatically if the second pass succeeds? -- Iñaki Úcar _______________________________________________ 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 on the list, report it: https://pagure.io/fedora-infrastructure
