On Wed, Jul 01, 2020 at 03:38:26PM +0200, Jan Kratochvil wrote: > On Wed, 01 Jul 2020 15:14:09 +0200, Stephen John Smoogen wrote: > > At the moment we have about 10% of the hardware > > we shipped back in operation and there are at least 2 to 3 weeks to > > get the rest up. Getting up larger builders is going to have to wait. > > Sure there is no hurry with larger builders. I watch this problem of missing > debuginfo for years. So, there's a lot of things we could do here... but I'd like to know more details: * Is this only on x86_64 that you need this? Or all arches? * you're guessing you need 160GB? Is that pretty accurate? The space on the builders currently has been somewhat constrained by the space we have available along with a desire to keep things pretty similar so we don't have 'special' machines. Of course thats already out the window as different arches and all the buildhw's are different machines. Short term we can probibly spin up a x86_64 builder with more disk space and direct chromium scratch builds there? Or... the buildhw-x86* machines actually have more disk than the buildvm-x86 vm's... but it's not fully allocated. I can fix that and they would have ~300GB or so each, would that be enough? in that case you could submit and cancel until you got a buildhw-x86 ? Finally as people mentioned upthread, koji has a concept called 'channels'. We already have a number of them. The hub has a policy config that can direct things to builders subscribed to specific channels. For example, all the livemedia tasks run on hosts in the livemedia channel. Before the move I created a 'heavybuilder' channel for chromium (official builds). This is because our normal aarch64 buildvm's take about 24-30 hours to build it, but we have 2 buildhw-a64's that have a ton of cpu and memory (but not much disk space so we can't put a lot of vm's on them). I just yesterday got this resetup. These builders take an hour or two to build aarch64 chromium. Anyhow, I'd suggest filing an infrastructure ticket with your needs and we can see what we can come up with either short or long term for you. kevin
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ 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
