-
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
Failed test SendAsync_CorrectVersionSelected_LoopbackServer #56026
Labels
Milestone
Comments
dotnet-issue-labeler
bot
added
area-System.Net.Http
untriaged
New issue has not been triaged by the area owner
labels
Jul 20, 2021
Tagging subscribers to this area: @dotnet/ncl Issue DetailsRandom timeout? I don't see an obvious timeout to increase.
|
Failures 5/20-7/27 (incl. PRs):
Likely recent regression, we should take a look in 6.0 |
karelz
changed the title
Failure in SendAsync_CorrectVersionSelected_LoopbackServer on Centos 8
Failed test SendAsync_CorrectVersionSelected_LoopbackServer
Jul 20, 2021
This was referenced Jul 29, 2021
alnikola
added a commit
that referenced
this issue
Jul 30, 2021
In case of an error aborting the connection, there is a race between a thread creating new `Http2Stream` to send a request and the thread looping in `ProcessIncomingFrames` that sets _shutdown flag and `_abortException`. If the request thread first sees `_shutdown == true`, then it won't see the `_abortException` even if it's set, so the request will be retried when it shouldn't. This PR adds `_abortException` check just before the `_shutdown == true` check to make sure an abort exception is observed. Fixes #1581 Fixes #56138 Fixes #56026
ghost
locked as resolved and limited conversation to collaborators
Aug 29, 2021
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Random timeout? I don't see an obvious timeout to increase.
https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-pull-55960-merge-56296aeca654468688/System.Net.Http.Functional.Tests/console.f68314b8.log?sv=2019-07-07&se=2021-08-08T21%3A40%3A56Z&sr=c&sp=rl&sig=gn3eeIXr5mCpUaeJAcNRg4RqUX8tDRnbOE2fhd1CT24%3D
#55960
The text was updated successfully, but these errors were encountered: