Disable some recently enabled HTTP3 tests #54843
Merged
geoffkizer merged 2 commits intodotnet:mainfrom Jun 29, 2021
Merged
Conversation
|
Tagging subscribers to this area: @dotnet/ncl |
Contributor
Author
|
/azp run runtime-libraries-coreclr outerloop |
|
Azure Pipelines successfully started running 1 pipeline(s). |
stephentoub
approved these changes
Jun 28, 2021
karelz
approved these changes
Jun 28, 2021
Contributor
Author
|
There is a metric crapload of HttpClient tests failing with TimeoutException on this PR. These failures must be unrelated to this PR, since all it does is disable tests. |
Member
Contributor
Author
|
It seems like all the TimeoutException failures are on Linux. |
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 #54806
Contributes to #54778
Disable the cookie tests temporarily again as they are flaky.
Disable a ConnectTimeout test permanently, as it doesn't make sense for HTTP3.