Uh oh!
There was an error while loading. Please reload this page.
Fix WinHttp StreamingTest backward compat Version - #104722
Conversation
Tagging subscribers to this area: @dotnet/ncl |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
liveans
commented
Jul 12, 2024
/azp run runtime-libraries-coreclr outerloop-windows |
|
Azure Pipelines successfully started running 1 pipeline(s). |
liveans
commented
Jul 12, 2024
This is ready for review, but I will wait until winhttp folks confirms the version over email, only after than that I'll merge this. |
Uh oh!
There was an error while loading. Please reload this page.
liveans
commented
Jul 12, 2024
/backport to release/8.0-staging |
Started backporting to release/8.0-staging: https://github.com/dotnet/runtime/actions/runs/9914519934 |
@liveans backporting to release/8.0-staging failed, the patch most likely resulted in conflicts: $ git am --3way --ignore-whitespace --keep-non-patch changes.patch
Applying: Add WS2022 to OsSupport check for Bidirectional Streaming
Applying: Enable the disabled test
error: sha1 information is lacking or useless (src/libraries/System.Net.Http.WinHttpHandler/tests/FunctionalTests/BidirectionStreamingTest.cs).
error: could not build fake ancestor
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0002 Enable the disabled test
Error: The process '/usr/bin/git' failed with exit code 128Please backport manually! |
@liveans an error occurred while backporting to release/8.0-staging, please check the run log for details! Error: git am failed, most likely due to a merge conflict. |
Fixes#103754
Server 2022 WinHttp supports the automatic chunking in HTTP/2 now, so our requests are going as
HTTP/2requests instead of falling back to HTTP/1.1.OSVersion doesn't report revision (reports it as 0) and build version will be 20348 for WS2022.