test: stabilize timer tests with FakeTimeProvider#10216
Merged
Conversation
Use FakeTimeProvider for the timer test cluster and drive timer ticks through diagnostic events instead of wall-clock delays. Inject TimeProvider into timer grains so callback delays are advanced deterministically by the tests. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
c548f8d to
9fe803a
Compare
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This was referenced Jun 14, 2026
This was referenced Jun 22, 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
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.
This fixes the timer test flake by removing wall-clock waits from the timer test flow. The timer test cluster now uses a FakeTimeProvider for grain timers, timer callback delays consume the injected TimeProvider, and tests drive callbacks using timer and callback diagnostic events so fake time is advanced only after the callback delay is registered.
Microsoft Reviewers: Open in CodeFlow