#8041 [CI] Builds stuck in f31-updates-candidate, no bodhi updates created
Closed: Duplicate 4 years ago by churchyard. Opened 4 years ago by churchyard.

Consider this build:

https://koji.fedoraproject.org/koji/buildinfo?buildID=1328778

I have not opted-in for gating, the advertised delay was supposed to be minutes. Yet here the build finished hours ago and there is no bodhi update.

(I am pretty sure I've built more packages that didn't show up, will post links later.)


This is basically a duplicate of https://pagure.io/fedora-infrastructure/issue/8037

Mass-rebuild is killing us :(

Metadata Update from @churchyard:
- Issue close_status updated to: Duplicate
- Issue status updated to: Closed (was: Open)

4 years ago

This is still happening: https://koji.fedoraproject.org/koji/builds?order=completion_time&tagID=6443&inherited=0&latest=1

My build finished more than an hour again, no bodhi update.

The mass rebuild is over.

Metadata Update from @churchyard:
- Issue status updated to: Open (was: Closed)

4 years ago

So,, the problem now is that the mass rebuild side tag is being merged into f31-pending... so robosign is checking every rpm and making sure signed copies of it are being written out. :(

Hopefully it will finish soon. You can look at number of builds in the f31-pending tag.

I don't really understand the procedure, are the packages signed twice?

no.

robosignatory was watching (along with all the other things) things tagged into f31-rebuild. If something was tagged into that, it would sign it and leave it in the tag. However, fedmsgs aren't 100% reliable, and during the early part of the mass rebuild it didn't have this config in place so it wasn't watching for those. Due to that, when we tag in the f31-rebuild, it was tagged into f31-pending instead of f31 directly. robosign then checks each build to make sure it's signed and written out before moving it to f31. If we didn't do this unsigned packages would land in f31 and break things.

OK. Lets close this again then. Hopefully things will get better after this finishes.

Metadata Update from @churchyard:
- Issue close_status updated to: Duplicate
- Issue status updated to: Closed (was: Open)

4 years ago

(And thanks for explaining that to me.)

I guess this is still ongoing?

BUILD: fedora-gather-easyfix-0.1.1-33.fc31 [1344214]
State: COMPLETE
...
Finished: Tue, 30 Jul 2019 08:28:01 CEST
Tags: f31-updates-candidate

(45 minutes ago at the time of this comment)

https://koji.fedoraproject.org/koji/builds?order=completion_time&tagID=6443&inherited=0&latest=1 has 118 builds

torbrowser-launcher-0.3.2-2.fc31 is there for couple days (probably really stuck)

python-deprecated-1.2.6-2.fc31 finished Mon, 29 Jul 2019 15:19:17 UTC

Login to comment on this ticket.

Metadata