Skip to content

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

Description

@runfoapp

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

Activity

  1. ghost added
    untriagedNew issue has not been triaged by the area owner
    on Feb 7, 2022
  2. elinor-fung commented on Feb 7, 2022

    @elinor-fung
    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).

  3. added
    disabled-testThe test is disabled in source code against the issue
    on Feb 9, 2022
  4. added this to the 7.0.0 milestone on Feb 10, 2022
  5. removed
    untriagedNew issue has not been triaged by the area owner
    on Feb 10, 2022
  6. wfurt commented on Feb 16, 2022

    @wfurt
    Member

    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

  7. elinor-fung commented on Feb 16, 2022

    @elinor-fung
    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.

  8. rzikm commented on May 2, 2022

    @rzikm
    Member

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

  9. reopened this on May 26, 2022
  10. buyaa-n commented on May 26, 2022

    @buyaa-n
    Contributor

    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]
    
  11. ghost added
    in-prThere is an active PR which will close this issue when it is merged
    on May 31, 2022
  12. ghost removed
    in-prThere is an active PR which will close this issue when it is merged
    on Jun 1, 2022
  13. removed their assignment
    on Jun 1, 2022
  14. rzikm commented on Jun 1, 2022

    @rzikm
    Member

    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.

  15. self-assigned this
    on Jul 27, 2022
  16. ghost added
    in-prThere is an active PR which will close this issue when it is merged
    on Jul 27, 2022
  17. ghost removed
    in-prThere is an active PR which will close this issue when it is merged
    on Jul 27, 2022
  18. ghost added
    in-prThere is an active PR which will close this issue when it is merged
    on Jul 27, 2022
  19. ghost removed
    in-prThere is an active PR which will close this issue when it is merged
    on Aug 2, 2022
  20. ghost locked as resolved and limited conversation to collaborators on Sep 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions