fix(test): bound local full-suite RAM#100437
Merged
Merged
Conversation
openclaw-barnacle
Bot
added
scripts
Contributor
Author
|
Land-ready at exact PR head Work completed:
Proof:
Known proof note: the separate serial per-leaf inventory connection expired after 38m48s, after capturing individual leaves up to 2.69 GiB RSS. The complete paired full-suite run above covers all 250 shards and is the landing proof. |
Contributor
Author
|
Merged via squash.
|
github-actions Bot
pushed a commit
to Desicool/openclaw
that referenced
this pull request
Jul 6, 2026
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.
Closes #100429
What Problem This Solves
Fixes an issue where developers running the full local test suite on roomy machines could experience excessive RAM pressure or OOM failures because the automatic profile multiplied its host-aware worker budget across nested Vitest processes.
Why This Change Was Made
The full-suite scheduler now spends the inferred host worker budget once across shard processes and keeps each shard to one Vitest worker. This removes the separate large/small nested profiles while preserving the ten-process ceiling, explicit operator overrides, memory/load throttling, and serial CI behavior.
User Impact
Default local full-suite runs use substantially less peak aggregate RAM and interfere less with other workstation workloads. Targeted tests, explicit concurrency overrides, and CI execution retain their existing contracts.
Evidence
node scripts/run-vitest.mjs test/scripts/vitest-local-scheduling.test.ts test/scripts/test-projects.test.tstbx_01kwsr7r7b5kpech5rd6vtp2ak; individual two-worker leaves reached 2.69 GB RSS.tbx_01kwss62hrm0qvyzrkvdde29aj: 22,907.4 MiB at 10 shards × 2 workers versus 13,722.1 MiB at 6 × 1, a 40.1% reduction. The final run passed and improved from 9m05s to 7m25s.origin/main: clean, no accepted or actionable findings (0.95 confidence).