-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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_ConnectionLimitNotReached_ConcurrentRequestsSuccessfullyHandled #41078
Comments
Tagging subscribers to this area: @dotnet/ncl |
Another failure mode of the same test:
Hit in #41234 |
Another failure:
#41358 |
failed again in job: runtime 20200827.91 Configurations: Error message
|
Again in #41908 @dotnet/ncl this seems to be causing fairly regular failures. |
cc: @alnikola |
I just hit this again in another PR. @ManickaP does that linked issue fix this? If not should we make this test outerloop today? |
And another PR hit. |
And another one #41908 |
I wouldn't make it outerloop because the root cause of the failure is not known yet, thus it can be an indicator of some production code issue. We need to investigate. |
@alnikola in that case we should disable it: as it is we are already ignoring it, but it is breaking unrelated CI jobs. |
I tried fixing it in #40844 by improving request handling code on the test server, but it seems there is some other issue. |
It still means you should disable it until you figure it out. We do not want to have tests that are frequently failing in CI. It is killing productivity of the team as a whole. |
Moved to: #45204 |
Created 2 new issues from this one since there's been yet another different failure reported here. Moving discussion about the offending test to #45204 |
The test is still failing. |
The test was disabled again by 8a6fa30 on 7/14 (the same day it was enabled by PR #55572) Failures on 7/14 while it was enabled:
Summary of known facts from history:
|
The test is still failing even with the latest fixes/changes (see #55730). |
failed in job: runtime 20200819.105
net5.0-Linux-Release-x64-CoreCLR_release-Ubuntu.1604.Amd64.Open
Error message
The text was updated successfully, but these errors were encountered: