Skip to content

ci: run the gate in parallel and reuse main's CI result at release - #452

Merged
vishr merged 7 commits into
mainfrom
ci/faster-gate
Nov 8, 2026
Merged

vishr merged 7 commits into
mainfrom
ci/faster-gate

Conversation

@vishr

@vishr vishr commented Nov 8, 2026

Copy link
Copy Markdown
Member

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.

  • Static checks, the Go suite and the race suite run as parallel jobs. The race suite is split across seven runners by scripts/go-race-shards.sh. A test checks that the runners cover every package exactly once.
  • A job named Gate keeps the required check. It always runs, and it fails unless every part succeeded, so a skipped or cancelled part cannot pass.
  • The plain Go suite stays because five test files build only without the race detector, and they hold the allocation and memory ceilings.
  • Container scan runs alongside Gate instead of after it. The browser smoke suite is split by viewport so each half stays well inside the 12-minute Playwright timeout.
  • just release waits for CI's push run on the exact commit instead of re-running the suites locally. The tag workflow reuses that result through scripts/ci-passed.sh, re-runs the dependency audit, and falls back to the full suites when no successful run exists.
  • just check covers the same 19 recipes as before, as check-static, test and ui-test.

Verification: just check and actionlint pass. This PR's own CI run gives the new timings.

vishr added 6 commits November 8, 2026 09:40
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
vishr enabled auto-merge (squash) November 8, 2026 18:53
@vishr
vishr merged commit 573c625 into main Nov 8, 2026
31 checks passed
@vishr
vishr deleted the ci/faster-gate branch November 8, 2026 19:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant