Repository navigation
Verify native readiness before cancellation probes - #14
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.
A post-merge local run exposed a cancellation probe that continued after an execution failed before readiness. Assert the native readiness marker explicitly and give only the cancellation probe a 25-second execution allowance within the existing 30-second test bound. Keep production defaults, native cancellation notification, process-reaping, cleanup-error, and single-terminal-event assertions unchanged. Three focused cancellation cases passed. This is synthetic test hardening only; no protocol/runtime behavior or deployment operations change.