fedora-infrastructure

#9046 src.fp.o commits don't show Koji builds
Closed: Fixed by pingou. Opened by churchyard.

Closed: Fixed
Reopen Issue

Describe what you would like us to do:

On src.fp.o commit list or commit details, the Koji builds are shown:

png

This is no longer happening for new builds. I am investigating what is my oldest build that doesn't show up. However, here are some recent examples:

f32:

https://koji.fedoraproject.org/koji/taskinfo?taskID=45850199
https://src.fedoraproject.org/rpms/python-pyqtchart/c/0a083bb1cbcdc17c6c3ff4aa3dbe1aa527ef7b14?branch=f32 (only shows the older rawhide build)

rawhide:

https://koji.fedoraproject.org/koji/taskinfo?taskID=45821764
https://src.fedoraproject.org/rpms/cura/c/7cedc9e7b8a9457b6f0ca013b74e95eb2939a086?branch=master (only shows the 4 older failed builds)

When do you need this to be done by? (YYYY/MM/DD)

Whenever possible.

Completed Mon, 08 Jun 2020 12:33:38 UTC
https://koji.fedoraproject.org/koji/taskinfo?taskID=45546232
https://src.fedoraproject.org/rpms/python-django/c/b7bb080de7a61e90b47bfd6ea1570727bd0f60df?branch=f31 has the link

Completed Tue, 09 Jun 2020 12:09:07 UTC
https://koji.fedoraproject.org/koji/taskinfo?taskID=45573475
https://src.fedoraproject.org/rpms/python-azure-sdk/c/10aa2fe16a135ad28309e1b496ce3a7e7f7756b1?branch=master misses the link

My guess is that the thing respponsible for this integration is broken since the migration?

This was done by loopabull which is not running currently.
We're going to replace it with toddlers.

This is tracked in: https://pagure.io/fedora-infrastructure/issue/9021

~~I don't think it's that simple, at least some builds seem to make it, e.g. mirrormanager2-0.14-2.fc33 (which I've built ~90 mins ago) is listed on src.fp.o.~~
Edited by nphilipp

@nphilipp I'm not seeing it here: https://src.fedoraproject.org/rpms/mirrormanager2/c/5a075b40b509fb5c3278f4034651350c5cb8a3ad?branch=master

~~Here's what I see when going to https://src.fedoraproject.org/rpms/mirrormanager2: [image snipped for brevity]~~
Edited by nphilipp

my bad, loopabull is running in iad2 but was stuck, I've restarted it

my bad, loopabull is running in iad2 but was stuck, I've restarted it

Thanks. Will it pick the old builds as well?

Here's what I see when going to https://src.fedoraproject.org/rpms/mirrormanager2:
Screenshot_from_2020-06-18_12-01-30.png

That's not what this ticket is about though ;-)

my bad, loopabull is running in iad2 but was stuck, I've restarted it

Thanks. Will it pick the old builds as well?

It should yes, it's been queueing thing into its own rabbitmq queue/server, so it's not catching up on them (one of the advantage of toddlers if that we have monitoring on the queue size, so we'll find out earlier when something like this happens)

Ah, sorry.

Edit: striking out my comments to reduce confusion.
Edited by nphilipp

https://src.fedoraproject.org/rpms/python-azure-sdk/c/10aa2fe16a135ad28309e1b496ce3a7e7f7756b1?branch=master caught up :)

It looks like it caught up, going to close as fix then :)

Toddlers should make things easier but let us know if this happens again!

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

Thank you @pingou.

Metadata
None
None
None
None
Lowest
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.