-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
add W11 test queue #58570
add W11 test queue #58570
Conversation
Tagging subscribers to this area: @dotnet/runtime-infrastructure |
We don't get individual tests but Quic had 547 test runs so it looks like MsQuic is in.
WinHttp tests are failing on Windows 11. Opened #58587 to track it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
cc @aik-jahoda as he is updating the test matrix. |
Looks like there are Win11-specific problems:
|
@@ -141,6 +141,7 @@ jobs: | |||
- ${{ if ne(parameters.jobParameters.isFullMatrix, true) }}: | |||
- Windows.81.Amd64.Open | |||
- Windows.10.Amd64.Server19H1.ES.Open | |||
- Windows.11.Amd64.ClientPre.Open |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cc @aik-jahoda
@@ -57,6 +57,9 @@ public static partial class PlatformDetection | |||
|
|||
public static bool IsWindows10Version2004Build19573OrGreater => IsWindowsVersionOrLater(10, 0, 19573); | |||
|
|||
// Windows 11 aka 21H2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this be just "IsWindows11OrLater" then?
iOS build timed out. Hard to imagine how it could be related. |
Do we want to take this for 6.0 @danmoseley? |
Yes we want this for 6.0 but I'm wondering if we want to backport all the queue changes together or separately? cc @aik-jahoda |
I don't know what is better. I started separately and end-up lumping other changes in as it was easier to verify that everything actually works. |
Given that this also enables WinHttpHandler to work correctly on Win11 (product change), I would like to get it into 6.0 RC2. |
Didn't know about the product change. In that case we should definitely get this in asap. @aik-jahoda is currently taking care of updating our queues to not run on EOL ones and test the ones that we actually support with .NET 6 and I expect that there will be more to backport (hopefully none product changes but who knows). |
Technically speaking, we can cut it out. But it was easier to fix the product than the tests - at least for main. |
These are still failing in other PRs, e.g. a recent console log. Is there any issue tracking it or should I open one? |
thanks. BTW I did run all the sockets tests locally and they seems ok. So far there is no indication this is product issue - more likely test problem. I know we run on v2 virtual HW and the timing may be different. |
Looks like q was already answered above, but yes we need the Win11 queue in 6.0, and probably much or possibly all of the other coverage adjustments @aik-jahoda is doing. Could be separately. |
Summary: backport this PR to release/6, is that correct and later merge rest of the CI matrix. @danmoseley is that correct? |
There is rest of Windows related CI matrix change: #58989 |
/backport to release/6.0 |
Started backporting to release/6.0: https://github.com/dotnet/runtime/actions/runs/1237958281 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
replaces #55298
Contributes to #55639
Contributes to #58587