Re: s390x builder outage

Neal Gompa <[email protected]>
Newsgroups gmane.linux.redhat.fedora.devel
Message-ID <CAEg-Je97zRuByPCq9Yx=w9-YeVSTYt4KiFeTxANPQBxu3CMsKQ@mail.gmail.com>
On Sun, Aug 16, 2026 at 5:51 AM Stephen J Smoogen
<[email protected]> wrote:
>
>
>
> On Sat, Aug 15, 2026, at 22:53, Neal Gompa wrote:
> > On Sat, Aug 15, 2026 at 6:30 PM Stephen J Smoogen
> > <[email protected]> wrote:
> >>
> >>
> >>
> >> On Sat, Aug 15, 2026, at 18:13, Chris Adams wrote:
> >> > Once upon a time, Fabio Valentini <[email protected]> said:
> >> >> It might also be worth noting that s390x is *already* kind of a
> >> >> second-tier architecture:
> >> >>
> >> >> - noarch builds are never scheduled to run on
> >>
> >> If I had to keep the architectures running, I would look at the problem differently… maybe there is an oversupply of resources for x86 and aarch64 plus an over demand of things wanting to be done. Cut those down to what the slowest arch and most easily overloaded arch
> >
> > We know there isn't an oversupply on x86 and ARM because if a couple
> > of boxes go down, then things slow down a lot there. So I would argue
> > we're probably treading water on those architectures today. And that
> > wasn't always the case.
> >
> >
>
> I can say that from 2009 til I left in 2021, we always seemed to never have enough x86. Every hardware refresh would give us some more speed and memory and that would disappear within a release cycle to the point of overload. If we had to drop a virtual host for repairs things would go off the rails. Keeping things running was very tied to the amount of work and knowledge that Kevin has on keeping things tuned. ( I say this from the number of times
> I “helped” and Kevin would have to fix or how things could blow up when Kevin went on vacation).
>

That aligns with my recollection as well. Thank you for your service. :)



-- 
真実はいつも一つ!/ Always, there's only one truth!
-- 
_______________________________________________
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.