Repository navigation
[ci-scan] Build break: macOS arm64 CoreCLR build exceeds 180-minute timeout #134870
Description
Activity
Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.I do not think we should be creating Known Build Errors for CI timeouts. Doesn't this risk allowing some PRs to merge with no actual test coverage runs?
Reacted by Radek ZikmundClosing based on the maintainer feedback: a whole-job timeout means the leg did not produce its intended coverage, so classifying it as a Known Build Error could incorrectly allow affected builds to appear accounted for. This should remain a visible CI failure rather than be matched by Build Analysis.
Note
This response was generated with the assistance of GitHub Copilot.
I do not think we should be creating Known Build Errors for CI timeouts. Doesn't think risk allowing some PRs to merge with no actual test coverage runs?
I will follow-up to see if we can improve the instructions, I didn't know copilot can now file KBEs when Agent Merge is enabled...
- added a commit that references this issue
on Oct 5, 2026
Build Information
Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1616210
Build error leg or test failing: osx-arm64 Debug CoreCLR_AllSubsets
Pull request: #133174
KBE authoring guidance (ci-failure-scan)
Error Detailsis for readers. The excerpt below is copied from the Azure Pipelines timeline issue.Error Message.ErrorPatternuses .NETSingleline | IgnoreCase | NonBacktrackingmatching with a 50ms-per-line timeout.BuildRetryis false so this issue does not request a CI rerun.ExcludeConsoleLogis true because this is an Azure Pipelines job-timeout issue rather than a Helix console failure.Error Details
The
Build productstep ran for 2 hours 44 minutes before cancellation. Its final output shows an ordinary restore followed by pipeline cancellation, with no compiler or product error. The PR changes are confined to System.Net TLS implementation and tests, so they do not explain this broad CoreCLR product-build timeout.Error Message
{ "ErrorMessage": "", "ErrorPattern": "^\\[osx-arm64 Debug CoreCLR_AllSubsets[^\\]]*\\] The job running on agent [^\\r\\n]* ran longer than the maximum time of 180 minutes\\.", "BuildRetry": false, "ExcludeConsoleLog": true }Agentic workflow metadata (ci-failure-scan)
Workflow artifact: ci-failure-scan
Artifact kind: kbe-verification
Verified match count: 1 hit in failure.log
Note
This issue was filed with the assistance of GitHub Copilot.
Known issue validation
Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=1616210
Error message validated:
[^\[osx-arm64 Debug CoreCLR_AllSubsets[^\]]*\] The job running on agent [^\r\n]* ran longer than the maximum time of 180 minutes\.]Result validation: ❌ Known issue did not match with the provided build.
Validation performed at: 9/29/2026 5:27:16 PM UTC
Report
Summary