On Mon, Jan 24, 2022 at 08:08:25PM +0100, Jakub Jelinek wrote: > On Mon, Jan 24, 2022 at 08:00:31PM +0100, Vitaly Zaitsev via devel wrote: > > On 24/01/2022 19:06, Kevin Fenzi wrote: > > > This seems kind of high, so we are going to resubmit all the failed > > > builds in a short second round to reduce the chance of transitory issues > > > causing the build failures. > > > > I think the ppc64 GCC regressions should be fixed first. > > Yeah. > The current state is that both the ppc64le long double related bugs have > been discussed with IBM, I have patches for both, bootstrapping/regtesting > them now on GCCFarm and am also doing a scratch koji build: > https://koji.fedoraproject.org/koji/taskinfo?taskID=81773481 > If the first testing looks ok, will submit them for upstream review, > if that is approved tonight or tomorrow will include those in tomorrow's > gcc rebuild (unlike the scratch build, that will include various other > fixes). But ETA from the build start is ~ 20 or more hours, so Wednesday. That seems long to wait for mass rebuild merging. I'd like to start trying to get composes and get the rebuilt packages out so people can start testing them/fixing fallout from the rebuild. Perhaps we could merge today and then do another pass of failed builds into f36-rebuild tag and merge that back on thursday or something? Can we easily identify those builds that failed due to these ppc64le issues? 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 on the list, report it: https://pagure.io/fedora-infrastructure
