enable two HTTP POST tests #94115
Merged
enable two HTTP POST tests #94115
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
wfurt
added
area-System.Net.Http
test-enhancement
|
Tagging subscribers to this area: @dotnet/ncl Issue Detailsfixes #1580 I have capture where the big upload took ~ 5minutes to complete. I don't know if that is my ISP, server load or infrastructure. So I enabled the tests and increased the default utmost for large posts.
|
|
/azp run runtime-coreclr outerloop |
|
Azure Pipelines successfully started running 1 pipeline(s). |
MihaZupan
approved these changes
Oct 27, 2023
|
yes, I saw that - The TCP window would fill up and shrink to 0 frequently. |
|
outer loop tets failures unrelated. |
ghost
locked as resolved and limited conversation to collaborators
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 #1580
I have capture where the big upload took ~ 5minutes to complete. I don't know if that is my ISP, server load or infrastructure. So I enabled the tests and increased the default utmost for large posts.
While it may seems excessive this is also OuterLoop test doing very large post to remote server so the actual performance may vary. I was running tests overnight in loop and I did not see failure after bumping the timeout up.