-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Test failure: System.Net.Http.Functional.Tests.SocketsHttpHandlerTest_Http2.Http2_MultipleConnectionsEnabled_InfiniteRequestsCompletelyBlockOneConnection_RemaningRequestsAreHandledByNewConnection #45204
Comments
Tagging subscribers to this area: @dotnet/ncl Issue Detailsfailed again in job: runtime 20200908.76 failed test: System.Net.Http.Functional.Tests.SocketsHttpHandlerTest_Http2.Http2_MultipleConnectionsEnabled_InfiniteRequestsCompletelyBlockOneConnection_RemaningRequestsAreHandledByNewConnection net5.0-Linux-Release-x64-CoreCLR_release-(Debian.10.Amd64.Open)[email protected]/dotnet-buildtools/prereqs:debian-10-helix-amd64-bfcd90a-20200121150006 Error message
Originally posted by @v-haren in #41078 (comment)
|
failed again in job: runtime 20201019.68 failed test: System.Net.Http.Functional.Tests.SocketsHttpHandlerTest_Http2.Http2_MultipleConnectionsEnabled_InfiniteRequestsCompletelyBlockOneConnection_RemaningRequestsAreHandledByNewConnection net6.0-Linux-Release-x64-CoreCLR_release-(Debian.10.Amd64.Open)[email protected]/dotnet-buildtools/prereqs:debian-10-helix-amd64-bfcd90a-20200121150006 Error message
Copied from: #41078 (comment) |
failed again in job: runtime 20201117.56 failed test: System.Net.Http.Functional.Tests.SocketsHttpHandlerTest_Http2.Http2_MultipleConnectionsEnabled_InfiniteRequestsCompletelyBlockOneConnection_RemaningRequestsAreHandledByNewConnection net6.0-Linux-Release-x64-CoreCLR_release-Debian.9.Amd64.Open Error message
Copied from: #41078 (comment) |
Originallly by @danmosemsft in #41078 (comment):
|
Originally by @alnikola in #41078 (comment):
|
I'm gonna look at Kusto what the stats are, but probably yeah, we'll disable this one as well in both branches. |
Much more prevalent on Linux, almost always it's 100s timeout on HttpClient when sending warmUp GET (stuck at response headers reading). The test itself is quite complex and I haven't been able to found potential source of the error --> I'll disable it for now, this needs deeper investigation. |
@danmosemsft Do you want me to backport the #45212 PR (disabling the test) to 5.0? |
@danmosemsft more open question, given that net5.0 isn't an LTS, how much effort should we spend on backporting test changes to it? |
There's 0 hits here @ManickaP @ViktorHofer. Do you think it's ok to close this one? |
The corresponding tests were disabled. I'll add the |
The test is disabled again from PR #55593 (on 7/13) Failures 6/29-7/13 (incl. PRs) ... while it was re-enabled:
|
Summary of test history:
|
The test is still failing even with the latest fixes/changes (see #55730). |
failed again in job: runtime 20200908.76
failed test: System.Net.Http.Functional.Tests.SocketsHttpHandlerTest_Http2.Http2_MultipleConnectionsEnabled_InfiniteRequestsCompletelyBlockOneConnection_RemaningRequestsAreHandledByNewConnection
net5.0-Linux-Release-x64-CoreCLR_release-(Debian.10.Amd64.Open)[email protected]/dotnet-buildtools/prereqs:debian-10-helix-amd64-bfcd90a-20200121150006
Error message
Originally posted by @v-haren in #41078 (comment)
Runfo Tracking Issue: http2_multipleconnectionsen
Build Result Summary
The text was updated successfully, but these errors were encountered: