spot reported a new issue against the project: `releng` that you are following: `` Look at https://koji.fedoraproject.org/koji/taskinfo?taskID=35542528
That build has been running for almost a week now, and all jokes about Chromium aside, it should not be alive, it should either be failed or complete. It is complete on x86_64 and i686, but on aarch64, it's running. Odd things:
* No errors in the build log * Multiple aarch64 buildroots (6)
Maybe something in the chromium build is causing the aarch64 environment to reboot? ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8456
kevin added a new comment to an issue you are following: `` So, the multiple buildroots are due to us restarting kojid (for various koji updates) which causes existing builds to restart...
How long does it normally take to finish on aarch64? The current build has been going since yesterday... and it does seem to actually be still building....
``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8456
The status of the issue: `Chromium can't build on aarch64, but doesn't fail either` of project: `releng` has been updated to: Closed as It's all good by spot.
spot added a new comment to an issue you are following: `` It finished this morning, so looks like I just had bad luck timing with the koji updates. Thanks. ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8456
rel-eng@lists.fedoraproject.org
-
Kevin Fenzi -
Tom Callaway