* Kevin Fenzi: > On Tue, Feb 01, 2022 at 05:27:22PM +0100, Florian Weimer wrote: >> <https://koji.fedoraproject.org/koji/taskinfo?taskID=82238153> failed >> with this error. What is going on there? >> >> I have tagged the glibc-2.34.9000-39.fc36 manually into >> f36-updates-candidate, which I assume will subject the build to gating. >> But it's still surprising. > > I suspect, but am not 100% sure, that this error was caused by koji > builders and hubs being different versions. I had downgraded the hubs to > 1.26.1 to avoid the failed tagging issue, but builders were still on > 1.27.1. > > I have now re-upgraded the hubs (with 1.27.1 + patch for the tagging > issue) so hopefully this just goes away. > > If anyone does see it again now, do let us know. Thanks, it just happened again: 82254171 build (f35-candidate, /rpms/glibc.git:b9f986221822180f163fca98bd0ae5d00a92938f^^): open (buildvm-s390x-18.s390.fedoraproject.org) -> FAILED: GenericError: cannot update build 1911183, state: COMPLETE This is glibc-2.34-22.fc35. Thanks, Florian _______________________________________________ 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
