-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Test failure: System.Net.Http.Functional.Tests.HttpClientHandlerTest_Http3.ServerClosesOutboundControlStream_ClientClosesConnection - Status code: Unknown (0xdde6f334) #75270
Comments
Tagging subscribers to this area: @dotnet/ncl Issue Details
I couldn't find more occurrences on 9/8 when looking at last 7 days in Runfo (there different symptoms). Error - Console log:
|
Triage: After @antonfirsov's changes we should not propagate QuicExeption -- this is weird, we should take a look. |
0xdde6f334 does not seem to be any QUIC Status code used in Linux, so this is highly suspicious. |
are there cases when the status is not errno @nibanks? |
I don't recognize the status code. Is this coming from stream shutdown event? If so, that means it's an application layer error code, not a platform/QUIC one. |
We don't use such values in our tests. Based on the callstack, the value is definitely coming from SHUTDOWN_COMPLETE.ConnectionCloseStatus (for app closure we throw different exception and the app error code comes from SHUTDOWN_COMPLETE.ConnectionErrorCode field). It could mean that we still have some memory corruption going on :/ |
Triage: check occurrence, close if not happening anymore. |
Happens occasionally, and passes on reruns. none of the recent failures had any weird weird MsQuic return code. I think we can close this safely. |
No |
Affected test:
System.Net.Http.Functional.Tests.HttpClientHandlerTest_Http3.ServerClosesOutboundControlStream_ClientClosesConnection
I couldn't find more occurrences on 9/8 when looking at last 7 days in Runfo (they have different symptoms).
Error - Console log:
The text was updated successfully, but these errors were encountered: