-
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.WinHttpHandlerFunctional.Tests.BidirectionStreamingTest.BackwardsCompatibility_DowngradeToHttp11 #103754
Comments
Tagging subscribers to this area: @dotnet/ncl |
Failed in: runtime-coreclr crossgen2 20240620.1 Failed tests:
Error message:
Stack trace:
|
The test disabled in #103797 |
Triage: heavily failing test, we need to investigate in 9.0. |
This issue started to happen because something has changed in Server2022, and WinHTTP started to send HTTP/2 requests instead of fallbacking to HTTP/1.1, added |
Removing Line 25 in 27e9b9d
Or adding a new feature check. This should be backported to 6.0 and 8.0 as well. |
Build Information
Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=713266
Build error leg or test failing: System.Net.Http.WinHttpHandlerFunctional.Tests.BidirectionStreamingTest.BackwardsCompatibility_DowngradeToHttp11
Pull request: https://github.com/dotnet/runtime.git/pull/103720
Error Message
Fill the error message using step by step known issues guidance.
Known issue validation
Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=713266
Error message validated:
[System.Net.Http.WinHttpHandlerFunctional.Tests.BidirectionStreamingTest.BackwardsCompatibility_DowngradeToHttp11 Assert.Throws() Failure: No exception was thrown
]Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 6/20/2024 11:09:58 AM UTC
Report
Summary
The text was updated successfully, but these errors were encountered: