Skip to content

[ci-scan] Hang: System.Net.WebSockets.Client.Tests times out on Apple (tvos/iossimulator) after 4500s #131317

Description

@github-actions

Build Information

Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1522836
Build error leg or test failing: tvos-arm64 Release AllSubsets_NativeAOT / iossimulator-x64 Release AllSubsets_CoreCLR - System.Net.WebSockets.Client.Tests

Error Details

[FAIL] System.Net.WebSockets.Client.Tests.SendReceiveTest_Invoker_Http2Loopback.ReceiveAsync_MultipleOutstandingReceiveOperations_Throws
[FAIL] System.Net.WebSockets.Client.Tests.AbortTest_SharedHandler_Loopback.ServerPrematureEos_ClientGetsCorrectException
fail: Run timed out after 4500 seconds

Error Message

{
  "ErrorMessage": [
    "System.Net.WebSockets.Client.Tests",
    "Run timed out after 4500 seconds"
  ],
  "ErrorPattern": "",
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}

Filed by ci-failure-scan (detection only). ci-failure-fix walks open [ci-scan] KBEs and either opens a small fix PR or comments here to loop in owners — it never disables the test.

Note

This issue was generated by an AI agent (GitHub Copilot / ci-failure-scan).

Warning

Firewall blocked 1 domain

The following domain was blocked by the firewall during workflow execution:

  • awmgmcpg

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "awmgmcpg"

See Network Configuration for more information.

Generated by CI Outer-Loop Failure Scanner · 733.7 AIC · ⌖ 15.6 AIC · ⊞ 18.6K · ◷

Report

Build Repository Test Pull Request
1629206 dotnet/runtime System.Net.WebSockets.Client.Tests.WorkItemExecution
1628879 dotnet/runtime System.Net.WebSockets.Client.Tests.WorkItemExecution
1628470 dotnet/runtime System.Net.WebSockets.Client.Tests.WorkItemExecution
1627529 dotnet/runtime System.Net.WebSockets.Client.Tests.WorkItemExecution
1625894 dotnet/runtime System.Net.WebSockets.Client.Tests.WorkItemExecution
1608288 dotnet/runtime System.Net.WebSockets.Client.Tests.WorkItemExecution

Summary

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

Activity

  1. added this to the 12.0.0 milestone on Jul 28, 2026
  2. dotnet-policy-service commented on Jul 28, 2026

    @dotnet-policy-service
    Contributor

    Tagging subscribers to 'os-tvos': @vitek-karas, @kotlarmilos, @steveisok, @akoeplinger
    See info in area-owners.md if you want to be subscribed.

  3. dotnet-policy-service commented on Jul 29, 2026

    @dotnet-policy-service
    Contributor

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

  4. github-actions commented on Jul 30, 2026

    @github-actions
    ContributorAuthor

    Workflow artifact: ci-fix
    Artifact kind: handoff
    Linked KBE: #131317

    Note

    AI/Copilot-generated triage note.

    This Known Build Error has no producible automated code change (reason: platform-specific hang/timeout — a whole System.Net.WebSockets.Client.Tests run times out after 4500s on Apple legs, which is a networking/runtime hang diagnosis rather than a mechanical edit), so I could not open even a best-effort PR. Looping in owners so it can be fixed forward rather than muted.

    Root cause (best analysis)

    On tvos-arm64 Release AllSubsets_NativeAOT and iossimulator-x64 Release AllSubsets_CoreCLR, the System.Net.WebSockets.Client.Tests assembly hits Run timed out after 4500 seconds. Two tests are implicated before the timeout: SendReceiveTest_Invoker_Http2Loopback.ReceiveAsync_MultipleOutstandingReceiveOperations_Throws and AbortTest_SharedHandler_Loopback.ServerPrematureEos_ClientGetsCorrectException. The whole-assembly timeout (not a single [FAIL]) indicates a hang — an outstanding receive/abort operation that never completes on the Apple HTTP/2 loopback path, blocking the run. Diagnosing whether this is an HTTP/2 loopback deadlock, an Apple-specific socket/TLS stall, or a NativeAOT-specific async continuation issue requires networking expertise and live repro; no safe mechanical diff is producible, and disabling is off the table.

    Evidence

    Suggested reviewers / area contacts

    • Area owners (area-System.Net): @karelz, @dotnet/ncl

    A fix would likely involve identifying the outstanding WebSocket receive/abort operation that hangs on the Apple HTTP/2 loopback path and ensuring it completes (or faults) so the run does not stall.

    Warning

    Firewall blocked 1 domain

    The following domain was blocked by the firewall during workflow execution:

    • awmgmcpg

    To allow these domains, add them to the network.allowed list in your workflow frontmatter:

    network:
      allowed:
        - defaults
        - "awmgmcpg"

    See Network Configuration for more information.

    Generated by CI Outer-Loop Failure Fixer · 287.5 AIC · ⌖ 18.4 AIC · ⊞ 17.4K · ◷

  5. removed
    blocking-clean-ciBlocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'
    on Sep 21, 2026
  6. jeffschwMSFT commented on Sep 21, 2026

    @jeffschwMSFT
    Member

    removing blocking-clean-ci as it has not failed in 30 days

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions