Speed up full integration with parallel agent lanes - #630
Merged
Merged
Conversation
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
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.
Summary
Replace the six serial full-integration shards with two parallel agent lanes: one Claude VM and one Codex VM. Each lane installs its agent once and runs every case for that agent serially.
The last successful #606 CI run took 14m18s, including 10m50s from the first full-journey job starting to the last one finishing:
https://github.com/databricks/unity-gateway/actions/runs/34920527726
The first revision passed all checks in 8m19s: 5m59s / 42% less time than that baseline, retaining all 39 live cases:
https://github.com/databricks/unity-gateway/actions/runs/34921778894
The follow-up also starts integration immediately alongside unit/agent e2e tests, removing the remaining agent-e2e startup barrier. The final required merge gate still waits for both suites and requires both to succeed. The new revision's CI will validate the additional speedup and increased request overlap.
Coverage and safety
fail-fast: false, per-case isolation/cleanup, evidence uploads, and the requiredtest/e2emerge gates.Validation
git diff --checkpassed.