Unquarantine ServerReset_BeforeRequestBody_ClientBodyThrows #57470
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Fixes dotnet#46717 There isn't an obvious race in the test and the component that timed out appears to be from runtime (`HttpClient` and/or `HttpContent`). Since the test hasn't failed in 30 days and runtime has likely changed in the 18 months since the issue was filed, I think we should unquarantine the test.
amcasey
requested review from
halter73,
BrennanConroy,
JamesNK and
mgravell
as code owners
dotnet-issue-labeler
bot
added
the
area-networking
JamesNK
approved these changes
Aug 22, 2024
amcasey
added a commit
that referenced
this pull request
Sep 24, 2024
captainsafia
pushed a commit
that referenced
this pull request
Dec 31, 2024
captainsafia
pushed a commit
that referenced
this pull request
Feb 11, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #46717
There isn't an obvious race in the test and the component that timed out appears to be from runtime (
HttpClientand/orHttpContent). Since the test hasn't failed in 30 days and runtime has likely changed in the 18 months since the issue was filed, I think we should unquarantine the test.