Closed wtgodbe closed 1 month ago
This test hasn't failed in the last 30 days.
This appears to be the call that was timing out: https://github.com/dotnet/aspnetcore/blob/ffd5a38ecc618cac8c424a78ea8f452779120276/src/Servers/Kestrel/test/InMemory.FunctionalTests/Http2/Http2ConnectionTests.cs#L5226
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, Http2FrameWriter.WriteGoAwayAsync
and WaitForConnectionErrorAsyncDoNotCloseTransport
appear to be called on the same thread.
As in #40626, I think the fact that the test is using an inline scheduler probably makes the original race impossible.
Failing Test(s)
Error Message
Stacktrace
Logs
Build
https://dev.azure.com/dnceng/public/_build/results?buildId=1715003&view=results