Skip to content

Fix flaky NoReconnectionToGatewayNotReturnedByManager test #9942

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
ReubenBond merged 1 commit into from
Feb 19, 2026
+5 −3
Merged

Fix flaky NoReconnectionToGatewayNotReturnedByManager test #9942

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
8 changes: 5 additions & 3 deletions test/Orleans.Runtime.Tests/ClientConnectionTests/GatewayConnectionTests.cs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -110,8 +110,10 @@ public override async Task InitializeAsync()
[Fact, TestCategory("Functional")]
public async Task NoReconnectionToGatewayNotReturnedByManager()
{
// Reduce timeout for this test
this.runtimeClient.SetResponseTimeout(TimeSpan.FromSeconds(1));
// Use a timeout shorter than OpenConnectionTimeout (5s) so that calls to
// the fake gateway produce a TimeoutException, but long enough that
// legitimate grain calls on slow CI machines don't spuriously timeout.
this.runtimeClient.SetResponseTimeout(TimeSpan.FromSeconds(3));

var connectionCount = 0;
var timeoutCount = 0;
Expand Down Expand Up @@ -157,7 +159,7 @@ public async Task NoReconnectionToGatewayNotReturnedByManager()

// Check that we only connected once to the fake GW
Assert.Equal(1, connectionCount);
Assert.Equal(1, timeoutCount);
Assert.True(timeoutCount >= 1, $"Expected at least 1 timeout but got {timeoutCount}");
}

[Fact, TestCategory("Functional")]
Expand Down
Loading