Skip to content

[QUIC] [Long Running Test] 'System.Net.Quic.Tests.QuicStreamConformanceTests.ReadWrite_Success' #103482

New issue
New issue
Closed
#118339
Closed
[QUIC] [Long Running Test] 'System.Net.Quic.Tests.QuicStreamConformanceTests.ReadWrite_Success'#103482
#118339
Labels
Known Build ErrorUse this to report build issues in the .NET Helix tabarea-System.Net.Quicos-macosmacOS aka OSXtest-run-coreTest failures in .NET Core test runs
Milestone
10.0.0

Description

@buyaa-n
buyaa-n
opened on Jun 14, 2024

Build Information

Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=707860
Build error leg or test failing: System.Net.Quic.Functional.Tests.WorkItemExecution
Pull request: https://github.com/dotnet/runtime.git/pull/103473
Failing Configuration: net9.0-osx-Debug-x64-coreclr_release-OSX.1200.Amd64.Open

Error Message

Fill the error message using step by step known issues guidance.

{
  "ErrorMessage": "",
  "ErrorPattern": "System.Net.Quic.Functional.Tests: [Long Running Test] 'System.Net.Quic.Tests.QuicStreamConformanceTests.ReadWrite_Success', Elapsed:",
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}

From log:

   System.Net.Quic.Functional.Tests: [Long Running Test] 'System.Net.Quic.Tests.QuicStreamConformanceTests.ReadWrite_Success', Elapsed: 00:02:10
   System.Net.Quic.Functional.Tests: [Long Running Test] 'System.Net.Quic.Tests.QuicStreamConformanceTests.ReadWrite_Success', Elapsed: 00:04:10
   System.Net.Quic.Functional.Tests: [Long Running Test] 'System.Net.Quic.Tests.QuicStreamConformanceTests.ReadWrite_Success', Elapsed: 00:06:11
   System.Net.Quic.Functional.Tests: [Long Running Test] 'System.Net.Quic.Tests.QuicStreamConformanceTests.ReadWrite_Success', Elapsed: 00:08:12
   System.Net.Quic.Functional.Tests: [Long Running Test] 'System.Net.Quic.Tests.QuicStreamConformanceTests.ReadWrite_Success', Elapsed: 00:10:13
   System.Net.Quic.Functional.Tests: [Long Running Test] 'System.Net.Quic.Tests.QuicStreamConformanceTests.ReadWrite_Success', Elapsed: 00:12:14

Known issue validation

Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=707860
Error message validated: [System.Net.Quic.Functional.Tests: [Long Running Test] 'System.Net.Quic.Tests.QuicStreamConformanceTests.ReadWrite_Success', Elapsed:]
Result validation: ❌ Known issue did not match with the provided build.
Validation performed at: 6/17/2024 11:36:29 AM UTC

Report

Summary

24-Hour Hit Count 7-Day Hit Count 1-Month Count
0 0 0

Activity

  1. buyaa-n
    added
    blocking-clean-ciBlocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'
    Known Build ErrorUse this to report build issues in the .NET Helix tab
    on Jun 14, 2024
  2. ghost added
    area-System.Net.Quic
    on Jun 14, 2024
  3. dotnet-policy-service
    added
    untriagedNew issue has not been triaged by the area owner
    on Jun 14, 2024

  4. dotnet-policy-service commented on Jun 14, 2024

    @dotnet-policy-service
    dotnet-policy-serviceBot
    on Jun 14, 2024 – with Dotnet Policy Service
    Contributor

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

  5. ManickaP
    changed the title [-]System.Net.Quic.Tests.MsQuicTests failure on CI[/-] [+][QUIC] [Long Running Test] 'System.Net.Quic.Tests.QuicStreamConformanceTests.ReadWrite_Success'[/+] on Jun 17, 2024

  6. ManickaP commented on Jun 17, 2024

    @ManickaP
    ManickaP
    on Jun 17, 2024
    Member

    Happens always on mac: osx.1200.amd64.open, there are some older errors like:

      Discovering: System.Net.Quic.Functional.Tests (method display = ClassAndMethod, method display options = None)
  Discovered:  System.Net.Quic.Functional.Tests (found 132 of 147 test cases)
  Starting:    System.Net.Quic.Functional.Tests (parallel test collections = on [6 threads], stop on fail = off)
MsQuic supported and using 'libmsquic.dylib 2.4.0.0 (e0385b047d7bd622319e9f6c4c00184a1294eea8)'.
    System.Net.Quic.Tests.MsQuicPlatformDetectionTests.UnsupportedPlatforms_ThrowsPlatformNotSupportedException [SKIP]
      Condition(s) not met: "IsQuicUnsupported"
    System.Net.Quic.Tests.MsQuicTests.QuicRootedConnectionGetsReleased_ConnectFails [SKIP]
      Condition(s) not met: "IsNotMonoRuntime"
    System.Net.Quic.Tests.MsQuicTests.QuicRootedObjectGetReleased [SKIP]
      Condition(s) not met: "IsNotMonoRuntime"
   System.Net.Quic.Functional.Tests: [Long Running Test] 'System.Net.Quic.Tests.QuicStreamConformanceTests.ReadWrite_Success', Elapsed: 00:02:01
   System.Net.Quic.Functional.Tests: [Long Running Test] 'System.Net.Quic.Tests.QuicStreamConformanceTests.ReadWrite_Success', Elapsed: 00:04:02
   System.Net.Quic.Functional.Tests: [Long Running Test] 'System.Net.Quic.Tests.QuicStreamConformanceTests.ReadWrite_Success', Elapsed: 00:06:03
   System.Net.Quic.Functional.Tests: [Long Running Test] 'System.Net.Quic.Tests.QuicStreamConformanceTests.ReadWrite_Success', Elapsed: 00:08:03
   System.Net.Quic.Functional.Tests: [Long Running Test] 'System.Net.Quic.Tests.QuicStreamConformanceTests.ReadWrite_Success', Elapsed: 00:10:04
   System.Net.Quic.Functional.Tests: [Long Running Test] 'System.Net.Quic.Tests.QuicStreamConformanceTests.ReadWrite_Success', Elapsed: 00:12:05
   System.Net.Quic.Functional.Tests: [Long Running Test] 'System.Net.Quic.Tests.QuicStreamConformanceTests.ReadWrite_Success', Elapsed: 00:14:06
['System.Net.Quic.Functional.Tests' END OF WORK ITEM LOG: Command timed out, and was killed]

    or the 2 newest (14.6. and 16.6.) with the many outputs (that are not failures), containing:

      Discovering: System.Net.Quic.Functional.Tests (method display = ClassAndMethod, method display options = None)
  Discovered:  System.Net.Quic.Functional.Tests (found 132 of 147 test cases)
  Starting:    System.Net.Quic.Functional.Tests (parallel test collections = on [6 threads], stop on fail = off)
MsQuic supported and using 'libmsquic.dylib 2.4.0.0 (e0385b047d7bd622319e9f6c4c00184a1294eea8)'.
...
   System.Net.Quic.Functional.Tests: [Long Running Test] 'System.Net.Quic.Tests.QuicStreamConformanceTests.ConcurrentBidirectionalReadsWrites_Success', Elapsed: 00:02:07
   System.Net.Quic.Functional.Tests: [Long Running Test] 'System.Net.Quic.Tests.QuicStreamConformanceTests.ConcurrentBidirectionalReadsWrites_Success', Elapsed: 00:04:09
   System.Net.Quic.Functional.Tests: [Long Running Test] 'System.Net.Quic.Tests.QuicStreamConformanceTests.ConcurrentBidirectionalReadsWrites_Success', Elapsed: 00:06:10
   System.Net.Quic.Functional.Tests: [Long Running Test] 'System.Net.Quic.Tests.QuicStreamConformanceTests.ConcurrentBidirectionalReadsWrites_Success', Elapsed: 00:08:12
   System.Net.Quic.Functional.Tests: [Long Running Test] 'System.Net.Quic.Tests.QuicStreamConformanceTests.ConcurrentBidirectionalReadsWrites_Success', Elapsed: 00:10:13
   System.Net.Quic.Functional.Tests: [Long Running Test] 'System.Net.Quic.Tests.QuicStreamConformanceTests.ConcurrentBidirectionalReadsWrites_Success', Elapsed: 00:12:15
['System.Net.Quic.Functional.Tests' END OF WORK ITEM LOG: Command timed out, and was killed]

    The tests are using MsQuic from main from 27.2.: microsoft/msquic@e0385b0
    We should probably prioritize #101590 for 9.0.

  7. ManickaP
    added
    os-macosmacOS aka OSX
    and removed
    untriagedNew issue has not been triaged by the area owner
    on Jun 17, 2024
  8. ManickaP
    added this to the 9.0.0 milestone on Jun 17, 2024

  9. ManickaP commented on Jun 17, 2024

    @ManickaP
    ManickaP
    on Jun 17, 2024
    Member

    First confirmed failed 28.5. (still has console log), but might be as old as 13.5. (no console logs anymore, but other attributes of the failure are the same).
    Query:

    Jobs
| join kind=inner WorkItems on JobId
| where Status == "Timeout" and FriendlyName == "System.Net.Quic.Functional.Tests" and not(Source has "/release/")
| project-away JobId, JobName, WorkItemId, JobId1, Name, Build, Creator, System, IsExternal, PullRequestId, Name1
| order by Finished desc
  10. karelz
    added
    test-run-coreTest failures in .NET Core test runs
    on Jun 25, 2024

  11. rzikm commented on Jul 8, 2024

    @rzikm
    rzikm
    on Jul 8, 2024
    Member

    I don't see any recent hits in Kusto, so I am inclined to close this issue.

  12. ManickaP commented on Jul 8, 2024

    @ManickaP
    ManickaP
    on Jul 8, 2024
    Member

    I don't see any recent hits in Kusto, so I am inclined to close this issue.

    I'm seeing it, e.g.: https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-pull-104543-merge-f453c7dc2ac94248a4/System.Net.Quic.Functional.Tests/1/console.a3c1723f.log?helixlogtype=result

    start Mon Jul 8 12:51:50 UTC 2024
...
System.Net.Quic.Functional.Tests: [Long Running Test] 'System.Net.Quic.Tests.MsQuicTests.BigWrite_SmallRead_Success', Elapsed: 00:02:09

  13. ManickaP commented on Jul 8, 2024

    @ManickaP
    ManickaP
    on Jul 8, 2024
    Member

    Ok that's a different test, but I found the exact one: https://helixre107v0xdeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-pull-104539-merge-3fdace35eeea425fa0/System.Net.Quic.Functional.Tests/1/console.3084f80c.log?helixlogtype=result

    start Mon Jul 8 08:15:06 EDT 2024
...
System.Net.Quic.Functional.Tests: [Long Running Test] 'System.Net.Quic.Tests.QuicStreamConformanceTests.ReadWrite_Success', Elapsed: 00:12:15

  14. liveans commented on Jul 18, 2024

    @liveans
    liveans
    on Jul 18, 2024
    Contributor

    It doesn't repro locally (ran test suite 10hrs straight, no hang), next step is probably creating a PR and collecting more info from CI machine.

  15. karelz
    modified the milestones: 9.0.0, 10.0.0 on Jul 25, 2024
  16. jeffschwMSFT
    removed
    blocking-clean-ciBlocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'
    on Jan 22, 2025

  17. jeffschwMSFT commented on Jan 22, 2025

    @jeffschwMSFT
    jeffschwMSFT
    on Jan 22, 2025
    Member

    removing blocking-clean-ci as this issue is not successfully matching the pattern

  18. ManickaP
    closed this as completedin #118339on Aug 4, 2025
  19. github-actions
    locked and limited conversation to collaborators on Sep 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Known Build ErrorUse this to report build issues in the .NET Helix tabarea-System.Net.Quicos-macosmacOS aka OSXtest-run-coreTest failures in .NET Core test runs

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions