fix(test): bound extension CLI subtest concurrency - #1127
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
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.
Problem and change
Release CI 36882765069 fails the macOS Node 24 extension policy test:
validateis terminated at its 20-second child-process deadline, returning 143 instead of 0.The outer test-file cap does not constrain
concurrency:truesubtest groups. The policy group launches 23 CLI cases at once, each potentially starting configuration workers. Bound all four CLI subtest groups in this file to two concurrent cases. Every case, assertion and timeout remains unchanged.Fixes #1126.
Verification
npm run verify: passed on macOS Node 26, including 1,397 root tests, workspace verification and integration proofs.Compatibility and security
Test scheduling only; no runtime, policy, sandbox, package or public behavior changes.