WebKitGTK builds have been unreliable for the past few weeks. There is
an infrastructure ticket for this here:
https://pagure.io/releng/issue/10909
I think processing debuginfo requires somewhere between 12-13 GB of
RAM, so the s390x builders are likely right on the threshold where it
will sometimes succeed and sometimes not.
You can see the build has been running for 52 hours, but the task is
only 6h30m as I write this. That's consistent with OOM. My guess is it
builds WebKit almost successfully, then dies processing debuginfo, then
starts building again, and just loops, wasting resources on the
builder. There is a related infrastructure ticket:
https://pagure.io/releng/issue/10910
Please note I am intend to retire the webkit2gtk3 package ASAP. In F37,
it will be obsoleted by a new webkitgtk source package, which builds
WebKitGTK three times. Of course that means the build time will triple,
but it will be easier to maintain than three different source packages.
A scratch build with all three builds enabled was actually successful.
For now, we're waiting to recover the package name:
https://pagure.io/releng/issue/10919
Michael
_______________________________________________
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
