Skip to content

.NET: Fix flaky MultiStepOperationTimeout unit test #10231

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Vincent Biret (baywet) merged 1 commit into from
Nov 10, 2026
Merged

.NET: Fix flaky MultiStepOperationTimeout unit test #10231

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion dotnet/tests/Microsoft.Agents.AI.UnitTests/Harness/MultiStepOperationTimeoutTests.cs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,9 +16,14 @@ public async Task RunStep_CompletedStepDoesNotResetTimeoutAsync()

// Act
int firstResult = timeout.RunStep(_ => 1);
await Task.Delay(200);

// Wait for the timer callback itself; a fixed delay can finish first on a loaded runner.
var expired = new TaskCompletionSource<bool>(TaskCreationOptions.RunContinuationsAsynchronously);
using CancellationTokenRegistration registration = timeout.Token.Register(() => expired.TrySetResult(true));
Task completed = await Task.WhenAny(expired.Task, Task.Delay(TimeSpan.FromSeconds(30)));

// Assert
Assert.Same(expired.Task, completed);
Assert.Equal(1, firstResult);
Assert.Throws<TimeoutException>(() => timeout.RunStep(_ => 2));
}
Expand Down
Loading