test: stabilize concurrent cancellation test - #10461
Merged
ReubenBond merged 1 commit intoAug 11, 2026
Merged
Conversation
Wait until every delayed interleaving call has started before cancellation, so grain-side cancellation evidence is guaranteed to exist. Preserve immediate cancellation coverage for the zero-delay case. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
GrainTaskMultipleCancellationscan complete caller-side cancellation before one or more requests begin executing, while its delayed cases later require every request to have recorded cancellation inside the grain. Slower activation after mixed runtime tests exposes that mismatch as a five-minute wait for evidence which can never exist.Add an interleaving start-notification path and wait until all delayed calls have entered the grain before scheduling cancellation. The zero-delay cases continue using the original path so pre-start cancellation remains covered, and the calls remain interleavable so concurrent cancellation behavior is preserved.
This completes the deterministic start barrier introduced for the single-call case in #10319.
Fixes #10432
Microsoft Reviewers: Open in CodeFlow