Repository navigation
ci: run the gate in parallel and reuse main's CI result at release - #452
Merged
Merged
Conversation
Gate ran every check, the Go suite and the race suite serially on one runner, taking 23 minutes. Static checks, the Go suite and the race suite now run in parallel, the race suite split across seven runners by scripts/go-race-shards.sh, and a Gate job keeps the required name and fails unless every part passed. Container scan runs beside Gate, and the browser smoke suite splits by viewport. A release no longer runs the suites twice more on a commit CI already verified: just release waits for CI's push run on that commit, and the tag workflow reuses its result, re-running the dependency audit and falling back to the full suites when no successful run exists.
Listing packages through with-duckdb.sh keeps the shard runners from fetching the dynamic DuckDB modules the static build never uses. ci-passed.sh waits for CI to register a just-pushed run and backs off when a watch fails at once. The contributor guide and hook comment now describe CI's parallel gate.
The first split put the MCP host specs with the 1100 viewports, which took 10 minutes against 4 for the 1440 half.
The MCP specs take 24 seconds; the 1100 viewport's accessibility and smoke specs are what took 10 minutes on the suite's single worker.
vishr
enabled auto-merge (squash)
November 8, 2026 18:53
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.
Gate ran every check, the Go suite and the race suite one after another on one runner, which took 23 minutes. A pull request waited about 26 minutes for its required checks, and a release spent 24 of its 30 minutes repeating tests on a commit CI had already verified.
scripts/go-race-shards.sh. A test checks that the runners cover every package exactly once.just releasewaits for CI's push run on the exact commit instead of re-running the suites locally. The tag workflow reuses that result throughscripts/ci-passed.sh, re-runs the dependency audit, and falls back to the full suites when no successful run exists.just checkcovers the same 19 recipes as before, ascheck-static,testandui-test.Verification:
just checkandactionlintpass. This PR's own CI run gives the new timings.