[H/3] Fix interop tests.#119497
Conversation
There was a problem hiding this comment.
Pull Request Overview
This PR fixes HTTP/3 interop tests that have been failing since August 25th due to Cloudflare returning 403 status codes instead of the expected 200 OK responses. The fix removes the status code assertions while preserving the core functionality tests.
Key Changes
- Removes HTTP status code assertions from two HTTP/3 interop test methods
- Maintains the essential HTTP/3 version verification to ensure protocol functionality
|
/azp list |
|
Tagging subscribers to this area: @dotnet/ncl |
|
/azp run runtime-libraries-coreclr outerloop |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/ba-g unrelated, the affected tests are not failing anymore.. |
|
/backport to 8.0-staging |
|
/backport to 8.0-staging |
|
Started backporting to 8.0-staging: https://github.com/dotnet/runtime/actions/runs/17606816408 |
|
/backport to 9.0-staging |
|
Started backporting to 9.0-staging: https://github.com/dotnet/runtime/actions/runs/17606820897 |
|
/backport to release/10.0 |
|
Started backporting to release/10.0: https://github.com/dotnet/runtime/actions/runs/17606829511 |
|
@ManickaP an error occurred while backporting to "8.0-staging", please check the run log for details! The process '/usr/bin/git' failed with exit code 1 |
|
@ManickaP an error occurred while backporting to "9.0-staging", please check the run log for details! The process '/usr/bin/git' failed with exit code 1 |
|
/backport to release/9.0-staging |
|
Started backporting to release/9.0-staging: https://github.com/dotnet/runtime/actions/runs/17606893993 |
|
/backport to release/8.0-staging |
|
Started backporting to release/8.0-staging: https://github.com/dotnet/runtime/actions/runs/17606898411 |
Based on Kusto data, since 25.8., interop test against cloudflare has been failing on the response status check (whether it's 200 OK, it's not, it's 403 now). We can either disable the test and lose coverage or just ignore the status. I chose the later since the status code in not relevant in evaluating whether HTTP/3 is working or not.
And we'll need to backport to all active release branches.