-
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 failures: System.Net.Http.Functional.Tests.HttpClientHandler_* / * - Azure endpoints #21665
Comments
Dupe in dotnet/corefx#19704 on 2017/5/12 Opened on behalf of @JiayiLi1 The test System.Net.Http.HttpRequestException : An error occurred while sending the request.\r
Build : Master - 20170512.01 (Portable Core Tests)
|
@CIPop can you please add all other dupes here? |
@danmosemsft That failure is different - please open a different bug for RedHat and that particular error: |
@CIPop will do, deleted my comment. |
There is plenty of dupes in just 1 week. @DavidGoll @CIPop @davidsh any pushback? |
Getting this error:
is impossible to diagnose unless we get a consistent repro. It can be caused by the Internet and/or test servers (on Azure) being slow to respond. It can also be caused by CI machines too busy to process a network I/O. While there are tests that run into this problem, calling a P0 isn't actionable right now unless we get a repro. |
This is P0 due to its impact on our ability to do business - it affects all CoreFX repo developers, all contributors. We need to work on it as P0-ish thing. That's an actionable thing. The bottom line is, that we can't live with flaky tests and keep doing further progress on the product. |
Note that GetAsync_AllowedSSLVersion_Succeeds repros on Win7 CI machines at a ~3% failure rate (see dup'd issue https://github.com/dotnet/corefx/issues/13281) |
This issue is repro on Portable Core Tests, detail: https://mc.dot.net/#/product/netcore/master/source/official~2Fcorefx~2Fmaster~2F/type/test~2Ffunctional~2Fportable~2Fcli~2F/build/20170522.01/workItem/System.Net.Http.Functional.Tests/wilogs |
NullReferenceException doesn't seem right, even in the face of a networking error. But it seems it may be from tests/xunit:
|
To make progress we could instrument the test with a Debug.Assert/Fail when this exception is raised and obtain a full-memory dump to look at the server-side. |
Following test: System.Net.Http.Functional.Tests.HttpClientHandler_MaxConnectionsPerServer_Test.GetAsync_MaxLimited_ConcurrentCallsStillSucceed failed with same issue, detail: https://ci.dot.net/job/dotnet_corefx/job/master/job/outerloop_netcoreapp_win7_debug/271/testReport/System.Net.Http.Functional.Tests/HttpClientHandler_MaxConnectionsPerServer_Test/GetAsync_MaxLimited_ConcurrentCallsStillSucceed_maxConnections__3__numRequests__2__secure__True_/ MESSAGE:
STACK TRACE:
|
It did not failed sine June. The non-managed failures were tracked here https://github.com/dotnet/corefx/issues/13281 |
This is tracking unreliable Azure infrastructure (Azure end points). Reopening. |
I'm getting very consistent timeouts for PostAsync_CallMethod_StreamContent with the same "System.Net.Http.WinHttpException : The operation has been canceled" timeout that is showing up for the rest of the test failures mentioned here. If you think it would help I can collect wireshark traces of the failure and share them.
|
That one is tracked primarily by dotnet/corefx#25902 and there's bunch of other tests with similar exception/error sets. |
Triage: We don't seem to be getting much value from this particular tracking issue. We're on top of Networking failures and there are many specific tracking bugs for the common failures. Closing. |
Multiple tests fail with the same stack indicating that the request took more than the configured (default=100s) timeout for HttpClient.
The reasons for this timeout may be different but in most cases the way the tests report the error makes it difficult (or impossible) to understand why the server didn't reply (or why the client didn't receive that reply).
OS Distribution:
Opened on behalf of @JiayiLi1
The test
System.Net.Http.Functional.Tests.HttpClientHandler_ServerCertificates_Test/NoCallback_RevokedCertificate_NoRevocationChecking_Succeeds
has failed.System.Net.Http.HttpRequestException : An error occurred while sending the request.\r
---- System.Net.Http.WinHttpException : The operation has been canceled
Build : Master - 20170512.01 (Core Tests)
Failing configurations:
Detail: https://mc.dot.net/#/product/netcore/master/source/official~2Fcorefx~2Fmaster~2F/type/test~2Ffunctional~2Fcli~2F/build/20170512.01/workItem/System.Net.Http.Functional.Tests/analysis/xunit/System.Net.Http.Functional.Tests.HttpClientHandler_ServerCertificates_Test~2FNoCallback_RevokedCertificate_NoRevocationChecking_Succeeds
The text was updated successfully, but these errors were encountered: