Microsoft.Quic.MsQuicException on rolling build of runtime

[mkhamoyan]

Description

Last build of runtime is failing with below exception on System.Net.Quic.Tests.MsQuicTests

System.AggregateException : One or more errors occurred. (Connection has been shutdown by transport: QUIC_STATUS_CONNECTION_REFUSED) ---- Microsoft.Quic.MsQuicException : Connection has been shutdown by transport: QUIC_STATUS_CONNECTION_REFUSED

Reproduction Steps

Check last rolling build of runtime

Expected behavior

System.Net.Quic.Tests.MsQuicTests should pass

Actual behavior

System.Net.Quic.Tests.MsQuicTests are failing

Regression?

No response

Known Workarounds

No response

Configuration

No response

Other information

No response

Tagging subscribers to this area: @dotnet/ncl
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Description

Last build of runtime is failing with below exception on System.Net.Quic.Tests.MsQuicTests

System.AggregateException : One or more errors occurred. (Connection has been shutdown by transport: QUIC_STATUS_CONNECTION_REFUSED) ---- Microsoft.Quic.MsQuicException : Connection has been shutdown by transport: QUIC_STATUS_CONNECTION_REFUSED

Reproduction Steps

Check last rolling build of runtime

Expected behavior

System.Net.Quic.Tests.MsQuicTests should pass

Actual behavior

System.Net.Quic.Tests.MsQuicTests are failing

Regression?

No response

Known Workarounds

No response

Configuration

No response

Other information

No response

Author:	mkhamoyan
Assignees:	-
Labels:	area-System.Net.Quic
Milestone:	-

[mkhamoyan]

@rzikm from commit log most probably it is related with #69603 , could you please take a look?

[rzikm]

I am looking into it, hopefully will be fixed with #69789

[rzikm]

No such luck, but the test failures seem to be confined to Windows 2022 Server, so I will disable the tests there meanwhile

[ManickaP]

Has the dotnet/msquic change been propagated via maestro already? When we update that repo, new version of windows version of libmsquic gets published into maestro subscription, which then creates PR in runtime in versions.xml, which then updates the msquic version.

Yeah, it wasn't consumed yet: #69709

[rzikm]

I find it a bit weird that the tests didn't fail on #69603 then. But we can wait a bit and see if the maestro PR resolves that.

[wfurt]

It actually did: https://github.com/dotnet/runtime/pull/69603/checks?check_run_id=6578113266 and https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-pull-69603-merge-e5a980b51f6847128e/System.Net.Quic.Functional.Tests/1/console.00373325.log?helixlogtype=result

But the test runs was marked as successful: cc @MattGal

[ManickaP]

Ha, Tomas is faster, yeah this was a trap 😄

[thhous-msft]

WS 2022 will not support client certificates using schannel. It was a feature added for Windows 11. The only way to get client certificate support on WS 2022 or earlier is to use OpenSSL.