SIGABRT in System.Net.Http.Functional.Tests on macOS

[jozkee]

Build Information

Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=1318374
Build error leg or test failing: System.Net.Http.Functional.Tests.WorkItemExecution
Pull request: #125133

Error Message

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

{
  "ErrorMessage": ["System.Net.Http.Functional.Tests","exit code 134 means SIGABRT Abort"],
  "ErrorPattern": "",
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}

Known issue validation

Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=1318374
Error message validated: [System.Net.Http.Functional.Tests exit code 134 means SIGABRT Abort]
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 3/3/2026 10:31:30 PM UTC

Report

Build	Repository	Test	Pull Request
1610307	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution
1610310	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution
1609584	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution	#134547
1610054	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution	#134561
1609947	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution
1609631	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution
1609437	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution
1609093	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution	#134405
1609099	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution
1607789	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution	#134461
1607772	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution	#134458
1606912	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution	#134405
1606680	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution
1606683	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution
1604549	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution	#134320
1601366	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution
1600593	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution	#134046
1600394	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution	#133445
1600261	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution	#133445
1599806	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution
1599465	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution	#134070
1598967	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution	#134046
1598686	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution
1598683	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution
1597679	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution	#133957
1597617	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution
1596989	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution
1596761	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution	#133623
1596746	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution
1596663	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution	#133445
1596101	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution	#133899
1595164	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution	#133623
1595158	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution
1595161	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution
1595019	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution	#133845
1594891	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution	#133839
1592126	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution
1576080	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution	#132996
1592073	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution
1591856	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution	#133623
1591859	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution
1591852	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution
1591829	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution
1591639	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution
1591376	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution	#133623
1591372	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution
1591369	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution
1589474	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution	#133512
1587976	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution	#133445
1586539	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution	#133385
1586540	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution	#133386
1586073	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution	#133364
1585541	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution
1582596	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution
1582506	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution
1581481	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution	#133114
1581899	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution
1581467	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution
1581270	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution	#133090
1581228	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution
1579259	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution	#133114
1579248	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution
1578993	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution	#133090
1577865	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution	#133055
1577359	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution	#133036
1576878	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution
1576052	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution	#132995
1574451	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution	#132959
1570294	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution
1570291	dotnet/runtime	System.Net.Http.Functional.Tests.WorkItemExecution

Summary

24-Hour Hit Count	7-Day Hit Count	1-Month Count
7	15	70

[dotnet-policy-service]

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

[mangod9]

here is the analysis from diag mcp:

Issue #125150 — Confirmed Facts

  The crash:

   - SIGABRT (exit code 134) in System.Net.Http.Functional.Tests on macOS
    14.7.2 x86_64 Intel
   - Happens ~6 seconds into test execution after exactly 7 identical SKIP messages
   - Confirmed on 3 different machines: dci-mac-build-258, -259, -263
   - No core dump (ulimit -c = 0), no macOS crash report uploaded
   - Both Debug and Release library configs crash

  Scope:

   - Only 1 of 246 Helix work items fails — System.Net.Http.Functional.Tests
   - All other assemblies pass, including System.Net.Security.Tests (1m 7s), System.Net.Sockets.Tests,
  System.Net.Quic.Functional.Tests
   - 1347 of 1791 tests discovered; 6 parallel threads running

  Causation:

   - First appeared ~March 3,
    2026. The "first failing build" PR (#125133) was only a version bump — the crash is not caused by any specific
  code change. It's an environment/platform change.
   - The checked coreclr configuration is a false comparison — it discovers 0/1791 tests due to [assembly:
  SkipOnCoreClr(..., ~RuntimeConfiguration.Release)] in the test's AssemblyInfo.cs, so it never actually validates
  that tests run.

  Code facts confirmed:

   - PlatformDetection.GetSsl3Support() returns true on all macOS (just return IsOSX) — no version check
   - GetTls10Support() and GetTls11Support() also return true for all IsOSXLike — no version check
   - GetTls13Support() explicitly returns false for macOS (there IS a version check there)
   - System.Net.Security.Tests creates TLS connections over in-memory streams (ConnectedStreams.CreateBidirectional),
   not real TCP sockets
   - System.Net.Http.Functional.Tests uses a real TCP loopback server (LoopbackServer.CreateServerAsync)

  ------------------------------------------------------------------------------------------------------------------

  Possible Causes

  Without a stack trace, none of these can be confirmed.

   1. Most likely — macOS
    14.7.2 dropped support for deprecated TLS protocols via real TCP. GetAsync_AllowedSSLVersion_Succeeds (in
  SocketsHttpHandler_HttpClientHandler_SslProtocols_Test) generates test cases for SSL3, TLS 1.0, and TLS 1.1 on
  macOS because PlatformDetection incorrectly says they're supported. When the test creates a real TCP loopback
  server with those protocols and calls SSLSetProtocolVersionMin(context, kSSLProtocol3/kTLSProtocol1) via the
  deprecated macOS SecureTransport API, it may abort. Security.Tests avoids this because it uses in-memory streams.
   2. Possible — macOS system update broke something else. The CI machines may have received a system update around
  March 3rd
    2026. The crash could be in a completely different code path that can't be identified without a stack trace.
   3. Cannot rule out — native assert in Apple crypto/TLS native shim. There is an assert(numCipherSuites < (1 <<
  16)) in pal_ssl.c and the file wraps all SSL APIs with #pragma clang diagnostic ignored
  "-Wdeprecated-declarations". If the assertions fire in a Debug native build, that would also explain SIGABRT.

  The highest-value next step would be enabling core dumps or collecting macOS crash reports from
  ~/Library/Logs/DiagnosticReports/ to get an actual stack trace.

[wfurt]

I don't see any recent failures. closing.