[ci-scan] Test failure: System.Net.Http.Functional.Tests.SocketsHttpHandlerTest_HttpClientHandlerTest_Http3.LargeUriAndHeaders_Works

[lewing]

Build Information

Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1623618
Build error leg or test failing: net11.0-windows-Release-x86-coreclr_release-Windows.Server2025.Amd64.Open - System.Net.Http.Functional.Tests
Pull request: #134958

KBE authoring guidance (ci-failure-scan)

• Error Details is for readers. The exception and stack trace below make the failure understandable without opening the raw log.
• Build Analysis parses only the single JSON block under Error Message.
• ErrorMessage uses case-sensitive ordinal substring matching against ordered log lines.
• BuildRetry is false because this is a test failure rather than a verified infrastructure retry case.
• ExcludeConsoleLog is false because both signature lines were verified in the Helix console log.

Error Details

System.Net.Http.Functional.Tests.SocketsHttpHandlerTest_HttpClientHandlerTest_Http3.LargeUriAndHeaders_Works [FAIL]
  System.AggregateException : One or more errors occurred. (An error occurred while sending the request.) (Stream aborted by peer (258).)
  ---- System.Net.Http.HttpRequestException : An error occurred while sending the request.
  -------- System.OutOfMemoryException : Insufficient memory to continue the execution of the program.
  ---- System.Net.Quic.QuicException : Stream aborted by peer (258).
  Stack Trace:
    /_/src/libraries/Common/tests/System/Threading/Tasks/TaskTimeoutExtensions.cs(87,0): at System.Threading.Tasks.TaskTimeoutExtensions.WhenAllOrAnyFailed(Task[] tasks)
    /_/src/libraries/Common/tests/System/Net/Http/GenericLoopbackServer.cs(44,0): at System.Net.Test.Common.LoopbackServerFactory.<>c__DisplayClass6_0.<CreateClientAndServerAsync>b__0(GenericLoopbackServer server, Uri uri)
    /_/src/libraries/Common/tests/System/Net/Http/Http3LoopbackServer.cs(114,0): at System.Net.Test.Common.Http3LoopbackServerFactory.CreateServerAsync(Func`3 funcAsync, Int32 millisecondsTimeout, GenericLoopbackOptions options)
    /_/src/libraries/Common/tests/System/Net/Http/HttpClientHandlerTest.cs(2384,0): at System.Net.Http.Functional.Tests.HttpClientHandlerTest.LargeUriAndHeaders_Works()

Error Message

{
  "ErrorMessage": [
    "System.Net.Http.Functional.Tests.SocketsHttpHandlerTest_HttpClientHandlerTest_Http3.LargeUriAndHeaders_Works [FAIL]",
    "System.OutOfMemoryException : Insufficient memory to continue the execution of the program."
  ],
  "ErrorPattern": "",
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}

Agentic workflow metadata (ci-failure-scan)

Workflow artifact: ci-failure-scan
Artifact kind: kbe-verification
Verified match count: 1 hits in failure.log

The existing macOS tracker #133729 covers a timeout in the same test, not this Windows x86 OutOfMemoryException and HTTP/3 peer-abort failure shape.

Note

This issue was generated with GitHub Copilot.

Known issue validation

Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=1623618
Error message validated: [System.Net.Http.Functional.Tests.SocketsHttpHandlerTest_HttpClientHandlerTest_Http3.LargeUriAndHeaders_Works [FAIL] System.OutOfMemoryException : Insufficient memory to continue the execution of the program.]
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 10/6/2026 9:23:26 AM UTC

Report

Build	Repository	Test	Pull Request
1623618	dotnet/runtime	System.Net.Http.Functional.Tests.SocketsHttpHandlerTest_HttpClientHandlerTest_Http3.LargeUriAndHeaders_Works	#134958

Summary

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

[dotnet-policy-service]

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