Skip to content

CI: split verify-tests into parallel spec shards - #211

Merged
woksin merged 2 commits into
mainfrom
ci-speed-split-verify-tests
Nov 12, 2026
Merged

woksin merged 2 commits into
mainfrom
ci-speed-split-verify-tests

Conversation

@woksin

@woksin woksin commented Nov 12, 2026

Copy link
Copy Markdown
Contributor

Changed

  • Pull request CI runs the unit specs as three parallel shards beside the contract, decorator and Library end-to-end checks, while the local yarn ci gate still runs every check (CI: split verify-tests #210).

verify-tests spent about six of its nine minutes in Vitest. The unit
specs now run in a three-way shard matrix next to the remaining contract,
decorator and Library end-to-end checks, and a guard spec pins every
original yarn ci command and the shard matrix.
@woksin woksin added the no-release No consumer-facing artifact changes label Nov 12, 2026
@woksin woksin self-assigned this Nov 12, 2026
@woksin
woksin merged commit c8f8391 into main Nov 12, 2026
15 of 16 checks passed
@cratis-direct
cratis-direct Bot deleted the ci-speed-split-verify-tests branch November 12, 2026 00:19
@woksin

woksin commented Nov 12, 2026

Copy link
Copy Markdown
Contributor Author

Measured after #211 merged (CI workflow, wall time from run creation to completion):

Run Wall Longest job
Before: PR run 43121035276 (after #209) 9.1 min verify-tests 8.8 min
After: PR run 43125825123 (#211) 4.0 min verify-specs (1/3) 3.6 min, verify-tests 3.5 min
After: main push run 43126396735 (c8f8391) 3.9 min verify-specs (1/3) 3.6 min

The Vitest suite now runs as three parallel shards (2.5–3.6 min each) next to the remaining verify-tests steps (2.4–3.5 min). Every other job stays at or below 3 min, so CI feedback is about 4 minutes, down from about 9. No spec coverage was removed; a guard test fails if a spec file is not assigned to exactly one shard.

@woksin woksin mentioned this pull request Nov 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

no-release No consumer-facing artifact changes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant