[mbien]

update: resurrecting this PR since it became useful for a different reason:

investigation showed that concurrency limits are enforced by label and we are fairly flexible on what arch we can test on.

switching from ubuntu-latest to ubuntu-26.04 or ubuntu-26.04-arm would be like a lane opening at the grocery store since each label is like an apache wide semaphore.

---

rumors say its faster, and it may also have a larger pool

this is just a benchmark for now to get stats for the three longest jobs

jobs:

• IDE Modules: difficult to say due to failures within retry scripts
• Java Hints batch1: 19m 41s -> 18m 25s
• Java Hints batch2: 13m 24s -> 14m 14s
• Java Modules: 50m 6s -> 44m 5s
• PHP: 48m 2s -> 46m 57s

[mbien]

Only minor differences. Was worth a try.

[mbien]

resurected this PR since there was a new discovery: the github concurrency limits are par label. and "ubuntu-latest" counts as a label. Since everyone is on the same label it is hit hardest.

running all tests (which started right away btw while the other jobs are waiting 5h already and counting)

arm failures:

• db job during container setup (arch mismatch)
• java/java.mx.project
  • it clones graal for some reason
• build system test (build all tests)
  • same reason as above

^^lets keep those on x64

[mbien]

java.mx.project Is actually a real failure. failing on master too. Lines up with the recent ubuntu update.

-> #9746