releng

#12885 buildSRPMFromSCM and noarch jobs needlessly stuck on s390x builders
Closed: Fixed with Explanation by kevin. Opened by churchyard.

Closed: Fixed with Explanation
Reopen Issue

I am building a large number of packages (~8k) with koji build ... --background. And I noticed the s390x jobs are often free (blue) for a very long time. That's OK.

However, some jobs that don't need to be s390x (buildSRPMFromSCM or noarch builds) unnecessarily get an s390x builder assigned and then wait for hours. While they could have easily be already finished, if only they had gotten a builder which is actually available.

Such jobs then also consume resources that would better be spent on real s390x builds.

So I wonder... why does Koji assign a s390x build, which is not available, to such tasks? Can we do something to limit this unfortunate behavior?

Metadata Update from @jnsamyak:
- Issue tagged with: investigation, medium-gain, medium-trouble, meeting

Right, thats because s390x is in our noarch_arches... and making srpms is a noarch task.

We could drop s390x from it, but when we set it up it was thought that there might be some advantage to running those there in case someone did something that broke the noarch packages on s390x.

But we could revisit this? I'm not sure how much real advantage it has...

Building noarch packages on s390x sometimes might be beneficial.

Building SRPMs on s309x is probably not.

But more generally, could it be made so that the s390x arch is assigned only when an s390x builder is available?

I don't think there is any way to seperate out buildsrpm noarch tasks from noarch tasks in general.

But I could easily be mistaken.

CC: @mikem

I don't think there is any way to seperate out buildsrpm noarch tasks from noarch tasks in general.

Yeah, the noarch_arches tag setting applies to all noarch tasks involving a buildroot for that tag.

We do have an outstanding issue to make this more flexible, but not on the roadmap yet. https://pagure.io/koji/issue/4235

Metadata Update from @kevin:
- Issue assigned to kevin

Given how much annoyance this is causing and that the advantages aren't super clear, I'm just going to remove s390x from noarch_arches at least for now.

We can revisit at some point...

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

Thanks!
Metadata

investigation medium-gain medium-trouble meeting

None
None
None
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.