chore: prune each arm's node_modules once its receipt is written - #35
Merged
Merged
Conversation
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.
Each benchmark arm runs
npm ciin its workspace and kept the result, about 300 MB per arm. Across the 21-24 Sep runs that came to 69 GB of untracked, lockfile-reproduciblenode_modules.run.mjsnow removesworkspace/node_modulesafter the final receipt is written. The answer, the agent's edits,diff.patch, receipts and logs stay, so rescoring (checkScopeis Git-only) and review are unaffected. Aborted arms keep theirs for debugging.Not exercised by a live benchmark run;
node --checkand the pre-pushnpm run checkpass.