On 09. 09. 20 23:20, Troy Dawson wrote:
It was a bit of a race condition. The automatic eln rebuilder got stuck, I'm not positive of the reason. But when it was restarted, it went through all of the package builds that it had missed, and built them. I'm not positive why, but if you look at the start times of the builds, python3.9-3.9.0~rc1-1.eln103 was started AFTER python3.9-3.9.0~rc1-2.eln103. By one minute.
python3.9-3.9.0~rc1-1.eln103: Started Fri, 14 Aug 2020 03:55:13 UTC Completed Fri, 14 Aug 2020 05:50:57 UTC python3.9-3.9.0~rc1-2.eln103: Started Fri, 14 Aug 2020 03:54:54 UTC Completed Fri, 14 Aug 2020 06:12:13 UTC Indeed, started first, even the buildID is lower. I somehow missed that, in the original email I claim that:
however there is no "more recent" (more recently started or more recently completed) build of python3.9 in Koji
And that was incorrect. Sorry about that.
Since ...rc1-2 was started before ...rc1-1, bodhi assumed that the one that started it's build last, was supposed to be the one that gets merged. Anyway, bodhi was just doing it's job, and it did it correctly. I think we need to look at our automation and when it get's stuck, make sure the backed up builds it does are in build order.
Right, that should do it. Considering the builds would not wait for each other to be visible in the buildroot anyway (unless the automation is that clever), even skipping the older builds in such situation might work (and save some resources).
Side note. I've manually tagged the new one into ELN.
Thanks. -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok _______________________________________________ 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
