-
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
[QUIC] Test .NET 7.0 on MsQuic 2.2 #83537
Comments
Tagging subscribers to this area: @dotnet/ncl Issue DetailsAfter MsQuic 2.2 will be released, we need to verify that updating from 2.1 to 2.2 will go seamlessly for all QUIC-supported platforms on .NET 7.0.
|
It seems like some test images already pick up the updates
I did not check all platforms but I would expect images that use package manager to converge on new version as they get rebuild. (AFAK full Helix VMs would also pick up updated on regular bases) I'm not sure if there is anything else left @CarnaViire. I'm not sure if we should update Windows to 2.2 as it is marked as pre-release |
7.0 release branch is running on Fedora 34 https://helixre107v0xd1eu3ibi6ka.blob.core.windows.net/dotnet-runtime-refs-heads-release-70-staging-5425e256aa714e7480/System.Net.Quic.Functional.Tests/1/console.7d4ef317.log?helixlogtype=result 😑 I'll verify stuff manually later. Windows part was not about updating right now, but to verify it works so in case of servicing we can just pull in the latest MsQuic instead of backporting a change. But it is just nice-to-have |
We have already released 7.0 which depends on msquic 2.2.2. Closing as solved. |
After MsQuic 2.2 will be released, we need to verify that updating from 2.1 to 2.2 will go seamlessly for all QUIC-supported platforms on .NET 7.0.
The text was updated successfully, but these errors were encountered: