Flaky Test: Timeout for RequestTests.ConnectionClosedTokenFiresOnServerFIN(listenOptionsName: "Loopback")

[TanayParikh]

Failing Test(s)

• Microsoft.AspNetCore.Server.Kestrel.Libuv.FunctionalTests.RequestTests.ConnectionClosedTokenFiresOnServerFIN(listenOptionsName: "Loopback")

Error Message

System.TimeoutException : The operation has timed out.

Stacktrace

   at Microsoft.AspNetCore.Testing.TaskExtensions.TimeoutAfter(Task task, TimeSpan timeout, String filePath, Int32 lineNumber) in /_/src/Shared/TaskExtensions.cs:line 143
   at Microsoft.AspNetCore.Server.Kestrel.Libuv.FunctionalTests.RequestTests.ConnectionClosedTokenFiresOnServerFIN(String listenOptionsName) in /_/src/Servers/Kestrel/test/FunctionalTests/RequestTests.cs:line 590
   at Microsoft.AspNetCore.Server.Kestrel.Libuv.FunctionalTests.RequestTests.ConnectionClosedTokenFiresOnServerFIN(String listenOptionsName) in /_/src/Servers/Kestrel/test/FunctionalTests/RequestTests.cs:line 598
--- End of stack trace from previous location ---

Logs

RequestTests_ConnectionClosedTokenFiresOnServerFIN-Loopback.log

Build

https://dev.azure.com/dnceng/public/_build/results?buildId=1434585&view=ms.vss-test-web.build-test-results-tab&runId=41430686&resultId=117917&paneView=debug

Thanks for contacting us.

We're moving this issue to the Next sprint planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[Tratcher]

This appears to be libuv specific and libuv has now been removed. Ready for unquarantine.