Repository navigation
[ci-scan] Test failure: System.Net.Quic MsQuicTests.ConnectWithCertificateForLoopbackIP_IndicatesExpectedError handshake timeout [Content truncated due to length] #134171
Description
Build Information
Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1598787
Build error leg or test failing: windows-x64 Release (libraries-jitstress)-System.Net.Quic.Tests.MsQuicTests.ConnectWithCertificateForLoopbackIP_IndicatesExpectedError
KBE authoring guidance (ci-failure-scan)
Error Detailsis for readers. Paste the full exception, stack trace, or build error excerpt so the failure is understandable without opening the raw log.- Build Analysis parses only the single JSON block under
Error Message. ErrorMessageis a case-sensitive ordinalString.Containssubstring copied verbatim from the failing log.- Set
BuildRetrytotrueonly for a clear infrastructure retry case.ExcludeConsoleLogdisables Helix console-log scanning.
Error Details
System.Net.Quic.Tests.MsQuicTests.ConnectWithCertificateForLoopbackIP_IndicatesExpectedError(ipString: "127.0.0.1", expectsError: True) fails under JIT stress: the QUIC connection handshake is cancelled by the 10-second configured timeout. Observed on the libraries-jitstress pipeline (definition 138), windows-x64 Release, across builds 1598787 and 1600498 on main.
System.Net.Quic.Tests.MsQuicTests.ConnectWithCertificateForLoopbackIP_IndicatesExpectedError(ipString: "127.0.0.1", expectsError: True) [FAIL]
System.Net.Quic.QuicException : Connection handshake was canceled due to the configured timeout of 00:00:10 seconds elapsing.
Stack Trace:
at System.Net.Quic.QuicConnection.<ConnectAsync>g__StartConnectAsync|2_0(QuicClientConnectionOptions options, CancellationToken cancellationToken)
at System.Net.Quic.Tests.QuicTestBase.CreateConnectedQuicConnection(...)
at System.Net.Quic.Tests.MsQuicTests.ConnectWithCertificateForLoopbackIP_IndicatesExpectedError(String ipString, Boolean expectsError)
Error Message
{
"ErrorMessage": [
"ConnectWithCertificateForLoopbackIP_IndicatesExpectedError(ipString: \"127.0.0.1\", expectsError: True) [FAIL]",
"System.Net.Quic.QuicException : Connection handshake was canceled due to the configured timeout of 00:00:10 seconds elapsing."
],
"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
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 filed by an AI agent (GitHub Copilot / ci-failure-scan).
Generated by CI Outer-Loop Failure Scanner · opus48 · 997.5 AIC · ⌖ 14.6 AIC · ⊞ 19.2K · ◷
Report
Summary
| 24-Hour Hit Count | 7-Day Hit Count | 1-Month Count |
|---|---|---|
| 2 | 9 | 9 |
Activity
dotnet-policy-service commentedon Sep 18, 2026
Tagging subscribers to this area: @karelz, @dotnet/ncl
See info in area-owners.md if you want to be subscribed.
github-actions commentedon Sep 18, 2026
Workflow artifact: ci-fix
Artifact kind: handoff
Linked KBE: #134171
Note
AI/Copilot-generated triage note.
This KBE has no safe automated diff: the expected-error MsQuic handshake times out only in
libraries-jitstress. Increasing the timeout would weaken regression detection rather than fix the codegen-stress behavior.Evidence
Suggested reviewers / area contacts
area-System.Net.Quic):@karelz,@dotnet/nclA fix likely identifies why JIT stress does not complete the expected-error handshake before cancellation.
Structured data:
{ "artifact_kind": "handoff", "linked_kbe": 134171, "workflow_artifact": "ci-fix" }VincentBu commentedon Sep 20, 2026
Failed in: runtime-coreclr libraries-jitstress 20260917.1
Failed tests:
Error message:
Stack trace:
kotlarmilos commentedon Sep 22, 2026
Closed as duplicate of #133645. Both reports cover
MsQuicTests.ConnectWithCertificateForLoopbackIP_IndicatesExpectedErrorfailing with the same ten-second handshake timeout and stack trace. The existing Known Build Error signature covers this occurrence.Note
This comment was generated by GitHub Copilot.