Well, or rather, it's not exactly that it's "versioned wrong", rather that for some reason, @submachine created an update for an older build when we already had an update for a newer build. 2.35-13 was done in June, I see no reason why an update was created for it now. I'm unpushing this.
Right. Looks like I created an update for f36 and f35 builds when it was only the f35 that needed that particular set of updates. That one went through. Sorry about the noise.
For help debugging failed Fedora CI tests (fedora-ci.*), contact the Fedora CI team.
For help debugging failed Fedora CoreOS tests (coreos.*), contact the Fedora CoreOS team.
For help debugging failed openQA tests (update.*), contact the Fedora Quality team, who will usually investigate and diagnose all failures within 24 hours.
This update has been submitted for testing by submachine.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'failed'.
This update is versioned wrong. It is two release tags lower than the current stable, glibc-2.35-15.fc36.
Well, or rather, it's not exactly that it's "versioned wrong", rather that for some reason, @submachine created an update for an older build when we already had an update for a newer build. 2.35-13 was done in June, I see no reason why an update was created for it now. I'm unpushing this.
Right. Looks like I created an update for f36 and f35 builds when it was only the f35 that needed that particular set of updates. That one went through. Sorry about the noise.