Conversation
Same three changes #379 made to integration.yml, applied to integration-mongodb, test, clippy, fmt, and licenses: runs-on extenddb_ubuntu-2404_4-core (pinned Ubuntu 24.04), a per-job timeout (30 min for the MongoDB suite whose longest job is 18 min; 15 min for the sub-5-minute workflows; licenses keeps its existing 20), and the corrected concurrency block — per-PR supersede on pull_request, run_id-unique groups for everything else so merge-group runs can never cancel one another.
robinnsc
requested review from
LeeroyHannigan,
amrith,
c33howard,
jcshepherd,
pdf-amzn and
yesyayen
as code owners
October 1, 2026 23:10
Collaborator
Author
|
Folded into #379 so the whole runner-pool migration is one review. The live runs on this branch already proved the pool for these five workflows (every job picked up in 24–26s). |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
The same three changes #379 made to
integration.yml, applied to the other five CI workflows (integration-mongodb,test,clippy,fmt,licenses):runs-on: extenddb_ubuntu-2404_4-coreon every job (9 jobs across the five files; zeroubuntu-latestremaining in CI workflows).timeout-minutes: 30 for the MongoDB suite (longest observed job 18 min across the last three main runs), 15 for the sub-5-minute workflows (test 3 min, clippy/fmt ~1 min);licenseskeeps its existing 20.pull_request; everything else keyed byrun_id. This is the fix from ci: move all CI workflows to the dedicated ExtendDB runner pool #379's audit: merge-group runs reuse a ref across re-queues and GitHub replaces a pending run in a group regardless ofcancel-in-progress, so ref-keyed groups could cancel merge-group runs.Independent of #379 (disjoint files); merge in either order.
Why
After this, every CI workflow in the repo runs on the dedicated pool, so nothing in the merge-group round competes with other orgs for runners — the full round is five fast workflows plus the two integration suites, all starting within seconds. Combined with #379 this is what makes the merge queue's 30-minute check timeout comfortably sufficient again.
Testing done
yaml.safe_loadon all five; 9runs-onswapped, timeouts present on every job, one concurrency block per file.pull_request, so every job below runs on the new pool. Confirm they start within a minute before approving.Checklist
ADR / RFC: n/a — CI infrastructure only.
Breaking changes
None.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache License 2.0 and I agree to the Developer Certificate of Origin (DCO). See CONTRIBUTING.md for details.