[ci-scan] Interpreter osx-arm64 recurring test crashes (SIGTRAP exit 133): System.Net.Requests.Tests

[github-actions]

Build Information

Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1413624
Pipeline: runtime-libraries-interpreter (definition 330)
Affected leg: osx-arm64 Release

Summary

Multiple library test suites consistently crash with SIGTRAP (exit code 133) on osx-arm64 when run under the Mono interpreter in the runtime-libraries-interpreter pipeline. The following tests fail in every build across the last 4 scanned builds:

• System.Net.Requests.Tests — 4/4 builds
• System.Net.WebSockets.Client.Tests — 4/4 builds
• System.Text.RegularExpressions.Tests — 3/4 builds

Additional intermittent crashes observed in System.IO.Pipelines.Tests, System.Text.Json.Tests, System.Net.HttpListener.Tests, System.Runtime.Tests, System.Runtime.Serialization.Formatters.Tests.

Error Message

{
  "ErrorMessage": "",
  "ErrorPattern": "Work item (System\\.Net\\.Requests\\.Tests|System\\.Net\\.WebSockets\\.Client\\.Tests|System\\.Text\\.RegularExpressions\\.Tests) in job .* has failed",
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}

Impact on platforms

• runtime-libraries-interpreter (def 330) · osx-arm64 Release · exit code 133 (SIGTRAP)
• Helix job examples: b99a75c8-4a90-4e59-85f0-9b33e7e62b14 (build 1413624)

First build it occurred

Present in all 4 builds scanned: 1413624 (May 8), 1410559 (May 6), 1407439 (May 4), 1405212 (May 1). True origin is likely earlier.

Occurrence count

4/4 builds in the scan window for System.Net.Requests.Tests and System.Net.WebSockets.Client.Tests.

Recommended action

This appears to be a systemic Mono interpreter issue on osx-arm64 that manifests as SIGTRAP crashes across multiple networking and regex test assemblies. Investigation should focus on the Mono interpreter's handling of platform-specific code paths on osx-arm64. The crash signals (SIGTRAP) suggest a debug trap or assertion in native code.

Warning

Firewall blocked 1 domain

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

• dotnet.github.io

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

network:
  allowed:
    - defaults
    - "dotnet.github.io"

See Network Configuration for more information.

Note

🔒 Integrity filter blocked 8 items

The following items were blocked because they don't meet the GitHub integrity level.

• #115515 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #117369 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #6385 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #7141 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #44158 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #5637 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #122721 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #107929 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".

To allow these resources, lower min-integrity in your GitHub frontmatter:

tools:
  github:
    min-integrity: approved  # merged | approved | unapproved | none

Generated by CI Outer-Loop Failure Scanner · ● 89.5M · ◷

[dotnet-policy-service]

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

[kotlarmilos]

Tracked in #128006 (consolidated; root cause is a CoreCLR interpreter GC assert, not Mono).