Skip to content
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

Merged
merged 7 commits into from
Sep 9, 2021
Merged

add W11 test queue #58570

merged 7 commits into from
Sep 9, 2021

Conversation

wfurt
Copy link
Member

@wfurt wfurt commented Sep 2, 2021

replaces #55298
Contributes to #55639
Contributes to #58587

@wfurt wfurt requested review from ViktorHofer and a team September 2, 2021 16:49
@wfurt wfurt self-assigned this Sep 2, 2021
@ghost
Copy link

ghost commented Sep 2, 2021

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

Issue Details

replaces #55298
contributes to #55639

Author: wfurt
Assignees: wfurt
Labels:

area-Infrastructure

Milestone: -

@ghost ghost added this to In Progress in Infrastructure Backlog Sep 2, 2021
@wfurt
Copy link
Member Author

wfurt commented Sep 2, 2021

We don't get individual tests but Quic had 547 test runs so it looks like MsQuic is in.

C:\h\w\9B9D08E2\w\A2950951\e>"C:\h\w\9B9D08E2\p\dotnet.exe" exec --runtimeconfig System.Net.Quic.Functional.Tests.runtimeconfig.json --depsfile System.Net.Quic.Functional.Tests.deps.json xunit.console.dll System.Net.Quic.Functional.Tests.dll -xml testResults.xml -nologo -nocolor -notrait category=IgnoreForCI -notrait category=OuterLoop -notrait category=failing  
  Discovering: System.Net.Quic.Functional.Tests (method display = ClassAndMethod, method display options = None)
  Discovered:  System.Net.Quic.Functional.Tests (found 140 of 150 test cases)
  Starting:    System.Net.Quic.Functional.Tests (parallel test collections = on, max threads = 2)
  Finished:    System.Net.Quic.Functional.Tests
=== TEST EXECUTION SUMMARY ===
   System.Net.Quic.Functional.Tests  Total: 547, Errors: 0, Failed: 0, Skipped: 0, Time: 60.849s

https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-pull-58570-merge-71d5888539224bb281/System.Net.Quic.Functional.Tests/1/console.817b7652.log?sv=2019-07-07&se=2021-09-22T18%3A25%3A20Z&sr=c&sp=rl&sig=ZUf%2BvlsRaiZhT8qXiJFDFL%2FkE%2BjPMYjAMKnuOtaIDiM%3D

WinHttp tests are failing on Windows 11. Opened #58587 to track it.

Copy link
Member

@ManickaP ManickaP left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@ViktorHofer
Copy link
Member

cc @aik-jahoda as he is updating the test matrix.

@karelz
Copy link
Member

karelz commented Sep 3, 2021

Looks like there are Win11-specific problems:

  • System.Net.Http.Functional.Tests.PlatformHandler_HttpClientHandler_SslProtocols_Test.GetAsync_AllowedSSLVersion_Succeeds - failed all 4 combinations of the test - see log
  • Sockets timed out 5 tests in SendPacketsAsync - see log:
    • SendPacketsElement_FileStreamMultiPartMixed_MultipleFileStreams_Success
    • SendPacketsElement_FileStreamLargeOffset_Throws
    • SendPacketsElement_FileStreamWithOptions_Success
    • SendPacketsElement_FileZeroCount_Success
    • SendPacketsElement_FileLargeOffset_Throws

@@ -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
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@@ -57,6 +57,9 @@ public static partial class PlatformDetection

public static bool IsWindows10Version2004Build19573OrGreater => IsWindowsVersionOrLater(10, 0, 19573);

// Windows 11 aka 21H2
Copy link
Member

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?

@danmoseley
Copy link
Member

iOS build timed out. Hard to imagine how it could be related.

@danmoseley danmoseley merged commit c515c50 into dotnet:main Sep 9, 2021
Infrastructure Backlog automation moved this from In Progress to Done Sep 9, 2021
@wfurt
Copy link
Member Author

wfurt commented Sep 9, 2021

Do we want to take this for 6.0 @danmoseley?

@ViktorHofer
Copy link
Member

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

@wfurt
Copy link
Member Author

wfurt commented Sep 9, 2021

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.

@karelz
Copy link
Member

karelz commented Sep 9, 2021

Given that this also enables WinHttpHandler to work correctly on Win11 (product change), I would like to get it into 6.0 RC2.
Is there any reason for NOT porting Win11 queue to 6.0 right now? (in which case we should separately port the WinHttpHandler product change needed)

@ViktorHofer
Copy link
Member

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).

@wfurt
Copy link
Member Author

wfurt commented Sep 9, 2021

Technically speaking, we can cut it out. But it was easier to fix the product than the tests - at least for main.
Win11 is first Windows OS where Tls13 is officially supported. So the gap did not matter until now.

@am11
Copy link
Member

am11 commented Sep 9, 2021

  • Sockets timed out 5 tests in SendPacketsAsync - see log:

These are still failing in other PRs, e.g. a recent console log. Is there any issue tracking it or should I open one?

@wfurt
Copy link
Member Author

wfurt commented Sep 9, 2021

Seems like flaky tests. Open issue @am11 if you see failures. @karelz is running some reports from test database so we should see it eventually.

@am11
Copy link
Member

am11 commented Sep 9, 2021

#58898

@wfurt
Copy link
Member Author

wfurt commented Sep 9, 2021

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.

@danmoseley
Copy link
Member

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.

@aik-jahoda
Copy link
Contributor

Summary: backport this PR to release/6, is that correct and later merge rest of the CI matrix. @danmoseley is that correct?

@aik-jahoda
Copy link
Contributor

There is rest of Windows related CI matrix change: #58989

@aik-jahoda
Copy link
Contributor

/backport to release/6.0

@github-actions
Copy link
Contributor

Started backporting to release/6.0: https://github.com/dotnet/runtime/actions/runs/1237958281

Copy link
Member

@safern safern left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@ghost ghost locked as resolved and limited conversation to collaborators Nov 3, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

8 participants