-
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
Flaky test: Http2_MultipleConnectionsEnabled_ConnectionLimitNotReached_ConcurrentRequestsSuccessfullyHandled #40436
Labels
area-System.Net.Http
blocking-clean-ci
Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'
test-bug
Problem in test source code (most likely)
Milestone
Comments
GrabYourPitchforks
added
area-System.Net.Http
test-bug
Problem in test source code (most likely)
blocking-clean-ci
Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'
labels
Aug 6, 2020
Tagging subscribers to this area: @dotnet/ncl |
Dotnet-GitSync-Bot
added
the
untriaged
New issue has not been triaged by the area owner
label
Aug 6, 2020
scalablecory
removed
the
untriaged
New issue has not been triaged by the area owner
label
Aug 6, 2020
alnikola
added a commit
that referenced
this issue
Aug 7, 2020
Jacksondr5
pushed a commit
to Jacksondr5/runtime
that referenced
this issue
Aug 10, 2020
Looks like the test is failing even after #40464 |
Failed again on net5.0-Linux-Debug-x64-CoreCLR_release-Centos.7.Amd64.Open
Again it's Libraries Test Run release coreclr Linux x64 Debug hit in #40729 |
alnikola
added a commit
that referenced
this issue
Aug 14, 2020
There are 2 flaky HTTP/2 tests verifying multiple connections feature which are randomly failing on CI, but not locally. - Http2_MultipleConnectionsEnabled_ConnectionLimitNotReached_ConcurrentRequestsSuccessfullyHandled - Http2_MultipleConnectionsEnabled_IdleConnectionTimeoutExpired_ConnectionRemovedAndNewCreated It seems the failure is caused by not reading the request body. In current implementation, `Http2LoopbackServer` read only HEADERS frame via `ReadRequestHeaderAsync` and then immediately sends response. However, the client firstly completely sends headers and body and only then starting reading a response. Thus, it seems to get blocked sometimes if the server didn't read the full body. This PR fixes this by calling `ReadAndParseRequestHeaderAsync` instead of `ReadRequestHeaderAsync`. Fixes #40436 Fixes #40115
ghost
locked as resolved and limited conversation to collaborators
Dec 7, 2020
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
area-System.Net.Http
blocking-clean-ci
Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'
test-bug
Problem in test source code (most likely)
Test Http2_MultipleConnectionsEnabled_ConnectionLimitNotReached_ConcurrentRequestsSuccessfullyHandled appears to be flaky. Occasionally timing out and causing CI failures.
See:
https://github.com/dotnet/runtime/pull/36252/checks?check_run_id=951684309
https://github.com/dotnet/runtime/pull/40426/checks?check_run_id=951565333
The text was updated successfully, but these errors were encountered: