Re: Old stalled bodhi updates

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, 2023-05-30 at 21:52 +0200, Mikel Olasagasti wrote:
> Hi all,
> 
> There are currently 157 updates in testing or pending status in Bodhi
> that were created before 2023:
> 
> https://bodhi.fedoraproject.org/updates/?search=&submitted_before=2023&status=pending&status=testing&page=1
> 
> There are 7 Fedora updates, 6 for Fedora-37 and one in
> pending->testing status for Fedora-35. The rest are for EPEL-7 and
> EPEL-8, mostly from before 2022, so I guess as those releases are
> still active the updates are not auto-closed.

Of the non-dummy F37 ones, two are stuck because they failed CI tests
that the package has marked as gating (required):

https://bodhi.fedoraproject.org/updates/FEDORA-2022-bf8feea173
https://bodhi.fedoraproject.org/updates/FEDORA-2022-826bb5fc42

in both cases, they failed the fedora-ci.koji-build.tier0.functional
test, which is from Fedora CI. In both cases the failure is old enough
that the logs are no longer available. We could hit the Re-Trigger
Tests button and see if they pass on a retry, or we could waive the
failures. CCing the maintainers (bcl and hadess).

https://bodhi.fedoraproject.org/updates/FEDORA-2022-2b17e1e469 is stuck because it was ejected from its initial push to testing,
which means the 7 day push to stable timer never really kicks in
(it needs to be *in testing* for seven days). It was supposedly left
out of the push because it didn't have the right tag. It does seem to
have the right tag now, at least, so I resubmitted it for testing. If
that works, it should then go stable a week later.

https://bodhi.fedoraproject.org/updates/FEDORA-2022-f563346d4d is
similar, but this time it was ejected from its push *to stable* (not to
testing), again allegedly for a missing tag. The builds have now
actually been deleted(!), so that update can never be pushed as-is, I
don't think. We would probably have to bump and rebuild both packages
and edit the new builds into the update, then try pushing it again.
CCing the maintainer of that one (Dan).
-- 
Adam Williamson (he/him/his)
Fedora QA
Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@xxxxxxxxxxxxx
https://www.happyassassin.net



_______________________________________________
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, report it: https://pagure.io/fedora-infrastructure/new_issue




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux