-
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
[6.0/8.0] Failure in BackwardsCompatibility_DowngradeToHttp11: no exception thrown #104390
Comments
Tagging subscribers to this area: @dotnet/ncl |
Same issue as #103754 |
@dotnet/ncl this is a very impactful change in servicing branches. Any chance you can take a look at this soon? |
I'm working on it, will get it merged soon. |
Thanks. Is it a product issue? Just a reminder that the code complete date is today at 4pm PT. |
Specifically for this test no. |
@liveans this is still happening in the 8.0 branch: https://github.com/dotnet/runtime/pull/105055/checks?check_run_id=27596364317 Reopening. |
Hmm or maybe not. I think the CI finished shortly before you merged your PR. Let me monitor the branch a couple more work days to confirm. |
We fixed |
Ah no, nevermind, you're right. I think it was fixed in the staging branch after the code complete day. I'll close this. |
Build Information
Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=719981
Build error leg or test failing:
System.Net.Http.WinHttpHandlerFunctional.Tests.BidirectionStreamingTest.BackwardsCompatibility_DowngradeToHttp11
Error Message
Libraries Test Run release coreclr windows x86 Release
Report
Summary
Known issue validation
Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=719981
Error message validated:
[System.Net.Http.WinHttpHandlerFunctional.Tests.BidirectionStreamingTest.BackwardsCompatibility_DowngradeToHttp11 [FAIL] No exception was thrown
]Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 7/3/2024 6:10:28 PM UTC
The text was updated successfully, but these errors were encountered: