Skip to content

Fix reminder churn test determinism - #9997

Merged
ReubenBond merged 1 commit into
dotnet:mainfrom
ReubenBond:fix-reminder-determinism
Apr 10, 2026
Merged

ReubenBond merged 1 commit into
dotnet:mainfrom
ReubenBond:fix-reminder-determinism

Conversation

@ReubenBond

@ReubenBond ReubenBond commented Apr 9, 2026 •

Copy link
Copy Markdown
Member

Root cause: the post-82fed1726dfa901dff008048204f9a0ce01ae476 tests mixed the new observer-driven waits with old timing assumptions. This lowers the guaranteed DEFAULT_REMINDER floor from 9 to 8, removes the last fixed-delay gate from the Azure/Cosmos 2J churn tests, and gives churn scenarios a dedicated timeout budget. Validation: dotnet build Orleans.slnx; ReminderEventsTests; focused Azure reminder filters for Rem_Azure_1J_MultiGrainMultiReminders and Rem_Azure_2J_MultiGrainMultiReminders.

Microsoft Reviewers: Open in CodeFlow

Adjust the churn reminder assertions and waiting logic to match the DiagnosticListener-based synchronization path. Replace the remaining fixed-delay gates in the Azure and Cosmos 2J churn tests with observed reminder activity and restore enough timeout budget for churn scenarios.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@ReubenBond
ReubenBond added this pull request to the merge queue Apr 10, 2026
Merged via the queue into dotnet:main with commit 7d52316 Apr 10, 2026
59 checks passed
@ReubenBond
ReubenBond deleted the fix-reminder-determinism branch April 10, 2026 15:44
@github-actions github-actions Bot locked and limited conversation to collaborators May 11, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant