On Thu, May 18, 2023 at 12:26:33PM -0700, Richard Henderson wrote: > So, here we are again, out of runner time with 13 days left in the month. > > Did we come to any resolution since last time? Holding development for that > long just > isn't right, so I'll continue processing the hard way -- testing on private > runners and > local build machines.
Hi Richard, We should have capacity for private runners to execute several jobs in parallel. Here [1] is an example of one that ran on a private runner today. I have been thinking about suggesting a strategy to run jobs that lend themselves to amd64 linux runners pinned to private runners that match, so more "shared" minutes can be spent on runners that have different capabilites. If there is another specific arch/OS runner you have in mind, I would be happy to make efforts towards provisioning one in our infrastructure. Particularly it seems like a lot of people are trying to use qemu to support amd64 linux on M1 macs, so it might make sense to have a private mac silicon macOS runner. Also, since we have a hardware runner that can run with kvm capabilites, it might make sense to carve some of those tests out for that tagged runner. Since this is relatively new, I think I was personally in an observational period before seeking input on those goals, but let me know you thoughts. Thanks, Eldon [1] https://gitlab.com/qemu-project/qemu/-/jobs/4310866300
