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.

Sign up for GitHub

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

Jump to bottom

System.Net.Quic.Functional.Tests timing out #64944

Closed
runfoapp bot opened this issue Feb 7, 2022 · 8 comments · Fixed by #70015
Closed

System.Net.Quic.Functional.Tests timing out #64944

runfoapp bot opened this issue Feb 7, 2022 · 8 comments · Fixed by #70015
Assignees
@rzikm
Labels
area-System.Net.Quic disabled-test The test is disabled in source code against the issue os-windows
Milestone
7.0.0

Comments

@runfoapp
Copy link

runfoapp bot commented Feb 7, 2022 •
edited
Loading

Runfo Tracking Issue: System.Net.Quic.Functional.Tests timing out

Build Definition Kind Run Name

Build Result Summary

Day Hit Count Week Hit Count Month Hit Count
0 0 0
@dotnet-issue-labeler
Copy link

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

@dotnet-issue-labeler dotnet-issue-labeler bot added the untriaged New issue has not been triaged by the area owner label Feb 7, 2022
@ghost
Copy link

ghost commented Feb 7, 2022

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

Issue Details

Runfo Tracking Issue: System.Net.Quic.Functional.Tests timing out

Build Definition Kind Run Name Console Core Dump Test Results Run Client
1597254 runtime-extra-platforms PR 64806 net7.0-windows-Release-x64-CoreCLR_release-Windows.Amd64.Server2022.Open console.log runclient.py
1596968 runtime-extra-platforms PR 64330 net7.0-windows-Release-x64-CoreCLR_release-Windows.Amd64.Server2022.Open console.log runclient.py
1596825 runtime-extra-platforms PR 64567 net7.0-windows-Release-x64-CoreCLR_release-Windows.Amd64.Server2022.Open console.log runclient.py
1596825 runtime-extra-platforms PR 64567 net7.0-OSX-Release-x64-CoreCLR_release-OSX.1200.Amd64.Open console.log
1596647 runtime-extra-platforms PR 64897 net7.0-windows-Release-x64-CoreCLR_release-Windows.Amd64.Server2022.Open console.log runclient.py
1596337 runtime-extra-platforms Rolling net7.0-windows-Release-x64-CoreCLR_release-Windows.Amd64.Server2022.Open console.log runclient.py
1595857 runtime-extra-platforms Rolling net7.0-windows-Release-x64-CoreCLR_release-Windows.Amd64.Server2022.Open console.log runclient.py
1595438 runtime-extra-platforms Rolling net7.0-windows-Release-x64-CoreCLR_release-Windows.Amd64.Server2022.Open console.log runclient.py
1594956 runtime-extra-platforms Rolling net7.0-windows-Release-x64-CoreCLR_release-Windows.Amd64.Server2022.Open console.log runclient.py
1594944 runtime-extra-platforms PR 64830 net7.0-windows-Release-x64-CoreCLR_release-Windows.Amd64.Server2022.Open console.log runclient.py
1594386 runtime-extra-platforms PR 62740 net7.0-windows-Release-x64-CoreCLR_release-Windows.Amd64.Server2022.Open console.log runclient.py
1594252 runtime-extra-platforms Rolling net7.0-windows-Release-x64-CoreCLR_release-Windows.Amd64.Server2022.Open console.log runclient.py
1593948 runtime-extra-platforms PR 64806 net7.0-windows-Release-x64-CoreCLR_release-Windows.Amd64.Server2022.Open console.log runclient.py
1593924 runtime-extra-platforms PR 64830 net7.0-windows-Release-x64-CoreCLR_release-Windows.Amd64.Server2022.Open console.log runclient.py
1593924 runtime-extra-platforms PR 64830 net7.0-windows-Release-x64-CoreCLR_release-Windows.Amd64.Server2022.Open console.log runclient.py

Build Result Summary

Day Hit Count Week Hit Count Month Hit Count
5 13 13
Author: runfoapp[bot]
Assignees: -
Labels:

untriaged, area-System.Net.Quic
Milestone: -

@elinor-fung
Copy link
Member

Logs don't seem to have much info, but I'd guess this is hitting the same problem on Windows Server2022 as in #64941.

  Starting:    System.Net.Quic.Functional.Tests (parallel test collections = on, max threads = 2)
   System.Net.Quic.Functional.Tests: [Long Running Test] 'System.Net.Quic.Tests.MsQuicTests.ConnectWithClientCertificate', Elapsed: 00:02:08
   System.Net.Quic.Functional.Tests: [Long Running Test] 'System.Net.Quic.Tests.MsQuicTests.ConnectWithClientCertificate', Elapsed: 00:04:08
   System.Net.Quic.Functional.Tests: [Long Running Test] 'System.Net.Quic.Tests.MsQuicTests.ConnectWithClientCertificate', Elapsed: 00:06:08
   System.Net.Quic.Functional.Tests: [Long Running Test] 'System.Net.Quic.Tests.MsQuicTests.ConnectWithClientCertificate', Elapsed: 00:08:08
   System.Net.Quic.Functional.Tests: [Long Running Test] 'System.Net.Quic.Tests.MsQuicTests.ConnectWithClientCertificate', Elapsed: 00:10:09
   System.Net.Quic.Functional.Tests: [Long Running Test] 'System.Net.Quic.Tests.MsQuicTests.ConnectWithClientCertificate', Elapsed: 00:12:09
   System.Net.Quic.Functional.Tests: [Long Running Test] 'System.Net.Quic.Tests.MsQuicTests.ConnectWithClientCertificate', Elapsed: 00:14:09
['System.Net.Quic.Functional.Tests' END OF WORK ITEM LOG: Command timed out, and was killed]

May want to also make these tests fail instead of just hanging (similar to #64943).

This was referenced Feb 8, 2022
Merged
Merged
Merged
Merged
@CarnaViire CarnaViire added the disabled-test The test is disabled in source code against the issue label Feb 9, 2022
@karelz karelz added this to the 7.0.0 milestone Feb 10, 2022
@karelz karelz removed the untriaged New issue has not been triaged by the area owner label Feb 10, 2022
@wfurt wfurt mentioned this issue Feb 16, 2022
Closed
@wfurt
Copy link
Member

wfurt commented Feb 16, 2022

I look at some of the logs and we seems to mix multiple issues here @elinor-fung

C:\h\w\B86009CA\w\B2970951\e>"C:\h\w\B86009CA\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  
error: Invalid IL code in (wrapper native-to-managed) System.Runtime.InteropServices.PosixSignalRegistration:HandlerRoutine (int): IL_0049: ret

This is from Windows 8.1 log and the test should even run there.

The actual hang seems specific to Windows.Amd64.Server2022 and should be investigated.
cc: @ManickaP

@elinor-fung
Copy link
Member

Ah, yeah. Sorry, the runfo query wasn't very filtered down. The Invalid IL code in (wrapper native-to-managed) issue is #65177. It affected every test on Mono on Windows and was fixed late last week.

@rzikm
Copy link
Member

rzikm commented May 2, 2022

No recent hangs of System.Net.Quic.Functional.Tests in test results DB. Closing

@rzikm rzikm closed this as completed May 2, 2022
@rzikm rzikm mentioned this issue May 25, 2022
Merged
@rzikm rzikm reopened this May 26, 2022
@rzikm rzikm mentioned this issue May 26, 2022
Merged
@buyaa-n
Copy link
Contributor

buyaa-n commented May 26, 2022

Same failures https://github.com/dotnet/runtime/pull/69815/checks?check_run_id=6615429005

  Starting:    System.Net.Quic.Functional.Tests (parallel test collections = on, max threads = 2)
    System.Net.Quic.Tests.MsQuicPlatformDetectionTests.UnsupportedPlatforms_ThrowsPlatformNotSupportedException [SKIP]
      Condition(s) not met: "IsQuicUnsupported"
    System.Net.Quic.Tests.QuicListenerTests_MockProvider.Listener_IPv6Any_Accepts_IPv4 [SKIP]
      Condition(s) not met: "IsMsQuicProvider"
   System.Net.Quic.Functional.Tests: [Long Running Test] 'System.Net.Quic.Tests.MsQuicTests.ConnectWithClientCertificate', Elapsed: 00:02:06
   System.Net.Quic.Functional.Tests: [Long Running Test] 'System.Net.Quic.Tests.MsQuicTests.ConnectWithClientCertificate', Elapsed: 00:04:06
   System.Net.Quic.Functional.Tests: [Long Running Test] 'System.Net.Quic.Tests.MsQuicTests.ConnectWithClientCertificate', Elapsed: 00:06:06
   System.Net.Quic.Functional.Tests: [Long Running Test] 'System.Net.Quic.Tests.MsQuicTests.ConnectWithClientCertificate', Elapsed: 00:08:06
   System.Net.Quic.Functional.Tests: [Long Running Test] 'System.Net.Quic.Tests.MsQuicTests.ConnectWithClientCertificate', Elapsed: 00:10:06
   System.Net.Quic.Functional.Tests: [Long Running Test] 'System.Net.Quic.Tests.MsQuicTests.ConnectWithClientCertificate', Elapsed: 00:12:06
   System.Net.Quic.Functional.Tests: [Long Running Test] 'System.Net.Quic.Tests.MsQuicTests.ConnectWithClientCertificate', Elapsed: 00:14:06
['System.Net.Quic.Functional.Tests' END OF WORK ITEM LOG: Command timed out, and was killed]

@buyaa-n buyaa-n mentioned this issue May 26, 2022
Merged
@naricc naricc mentioned this issue May 27, 2022
Merged
@rzikm rzikm mentioned this issue May 31, 2022
Merged
@ghost ghost added in-pr There is an active PR which will close this issue when it is merged and removed in-pr There is an active PR which will close this issue when it is merged labels May 31, 2022
@rzikm rzikm removed their assignment Jun 1, 2022
@rzikm
Copy link
Member

rzikm commented Jun 1, 2022

Tests are disabled for now, they seem to fail in windows.11.amd64.client.open even after updating to newest MsQuic. Putting this on hold until we have more time to investigate.

@rzikm rzikm self-assigned this Jul 27, 2022
@ghost ghost added in-pr There is an active PR which will close this issue when it is merged and removed in-pr There is an active PR which will close this issue when it is merged labels Jul 27, 2022
@ghost ghost removed the in-pr There is an active PR which will close this issue when it is merged label Aug 2, 2022
@ghost ghost locked as resolved and limited conversation to collaborators Sep 1, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@rzikm rzikm

Labels
area-System.Net.Quic disabled-test The test is disabled in source code against the issue os-windows
Projects
None yet
Milestone
7.0.0
Development

Successfully merging a pull request may close this issue.

Enable MsQuicTests.ConnectWithClientCertificate on Windows rzikm/dotnet-runtime
6 participants
@CarnaViire @karelz @wfurt @rzikm @buyaa-n @elinor-fung