-
Notifications
You must be signed in to change notification settings - Fork 10.3k
Quarantine AcceptNewStreamsDuringClosingConnection #41172
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.
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
Comments
This test hasn't failed in the last 30 days. |
This appears to be the call that was timing out: aspnetcore/src/Servers/Kestrel/test/InMemory.FunctionalTests/Http2/Http2ConnectionTests.cs Line 5226 in ffd5a38
|
Curiously, the log above shows that, after the 30 second timeout, the server did actually send the desired GOAWAY. It's hard to believe it could have fired immediately after the timeout by coincidence. Maybe there's some reason it was blocked until the timeout completed? |
In at least a few runs, |
As in #40626, I think the fact that the test is using an inline scheduler probably makes the original race impossible. |
It hasn't failed in 30 days and code inspection suggests it can't fail in the same way as it did two years ago. Fixes dotnet#41172
It hasn't failed in 30 days and code inspection suggests it can't fail in the same way as it did two years ago. Fixes #41172
It hasn't failed in 30 days and code inspection suggests it can't fail in the same way as it did two years ago. Fixes #41172
Failing Test(s)
Error Message
Stacktrace
Logs
Build
https://dev.azure.com/dnceng/public/_build/results?buildId=1715003&view=results
The text was updated successfully, but these errors were encountered: