test: cap Vitest workers for parallel worktrees - #1710
Merged
Merged
Conversation
Size Report
Startup median (7 runs, lower is better):
Top changed chunks: no changes in the largest emitted chunks. |
Member
Author
|
Exact-head review at No label applied by this reviewer. |
|
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.
Summary
Cap default Vitest concurrency at two workers so three concurrent Codex worktrees leave CPU headroom for test subprocesses, simulators, and the OS on a 12-core development host.
Use the same shared cap for affected coverage runs. The subprocess-stub project remains serialized at one worker.
Scope: 5 files; test-runner configuration and its regression coverage only.
Validation
The full unit bundle passed under three concurrent Codex workers: 680 files and 5,913 tests in 221.81s. Node integration passed 55 tests with 8 live-device cases skipped, and provider integration passed 156 tests. Affected coverage, integration progress, replay compatibility, formatting, lint, typecheck, layering, fallow, build, and package verification passed.
Red-before proof: removing only the new top-level cap makes the config regression fail with undefined !== 2; restoring it passes.
The package smoke initially timed out in the host Apple inventory probe after broad validation but passed in isolation. The final affected gate passed with xcrun unavailable, matching the package check stated device-free/offline contract.
No command behavior, docs, or skills changed.