Repository navigation
test: verify Windows Provider cancellation and descendant cleanup - #40
Merged
Merged
Conversation
This was referenced Oct 20, 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.
The startup suite previously skipped cancellation on Windows while covering its Job Object timeout path. Run the cancellation case on Windows too: allocate a console when the runner is headless, start a process group, send Ctrl+Break, and require exit 130, a structured cancellation error, lock release and terminated descendants.
This completes the cross-platform cancellation check for the already released 2026.10.20.2 implementation. No runtime or release payload changes. Local POSIX tests pass; native CI exercises both Windows baselines, macOS and Linux. Self-review checked process-group targeting and independent descendant liveness checks.