-
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
Enable Http2_MultipleConnectionsEnabled_InfiniteRequestsCompletelyBlockOneConnection_RemaningRequestsAreHandledByNewConnection test #54683
Conversation
Tagging subscribers to this area: @dotnet/ncl Issue Details
|
Test |
did you run whole set or just the single test @alnikola ? |
I ran only this test but through [MemberData]. |
These will likely be affected by my connection pooling changes. If you want, I can just re-enable them in my PR (if they look clean on my machine). |
@geoffkizer I'd enable them in a separate PR to make issues backtracking easier. But if you'd like it more, then go ahead and enable it in your PR. |
anything flaky needs to be run as whole bundle @alnikola. Many tests would always pass when executed in isolation but may fail when completing for resources with other test. |
@alnikola Makes sense, go ahead and enable them. |
@wfurt Are talking about running only the test class owning this test (i.e. |
What about Http2_MultipleConnectionsEnabled_IdleConnectionTimeoutExpired_ConnectionRemovedAndNewCreated also? |
Test |
This test is failing locally. I'm investigating it. |
I would run the whole System.Net.Http.FunctionalTests as CI would - just locally so it is more under controlled environment. |
OK, it makes sense. I will try it. |
I ran the whole System.Net.Http.FunctionalTests test set locally for ~30 mins and everything completed successfully. |
/azp run runtime-libraries-coreclr |
No pipelines are associated with this pull request. |
/azp run runtime-libraries-coreclr innerloop |
No pipelines are associated with this pull request. |
Unfortunately,
|
However, it seems that the test job itself timed out and was terminated, so it might be it wasn't an actual test failure. |
…ncurrentRequestsSuccessfullyHandled
I will enable only |
Fixes #45204