-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[HTTP/3] SocketsHttpHandlerTest_Http3_MsQuic.ClientSettingsReceived_Success timing out #55774
Comments
Tagging subscribers to this area: @dotnet/ncl Issue DetailsFailure query Test failures typically have the following call stack
Note: thus far this has only failed in Pull Requests so it's not definitively a bug. However the PRs aren't networking related to my understanding hence seems more likely it is a bug here. It's also hit 14 times now.
|
Triage: 27 occurrences so far, we might disable it. For 6.0 we need to at least rule out whether it's product bug
|
Failures 5/17-7/16 (incl. PRs):
We should disable it at least on Fedora ASAP to avoid creating noise for everybody in PRs. runtime/src/libraries/System.Net.Http/tests/FunctionalTests/HttpClientHandlerTest.Http3.cs Line 78 in 9a9b105
|
…ccess test Started failing too frequently - see #55774
…ccess test (dotnet#55811) Started failing too frequently - see dotnet#55774
Re-enabled in #67418, no occurrences in Kusto. |
Failure query
https://runfo.azurewebsites.net/search/tests/?q=started%3A~7%20definition%3Aruntime%20name%3A%22system.net.http.functional.tests.socketshttphandlertest_http3_msquic.clientsettingsreceived_success%22
Test failures typically have the following call stack
Note: thus far this has only failed in Pull Requests so it's not definitively a bug. However the PRs aren't networking related to my understanding hence seems more likely it is a bug here. It's also hit 14 times now.
The text was updated successfully, but these errors were encountered: