Repository navigation
[ci-scan] Build break: cDAC dump generation failures in runtime-diagnostics #131979
Description
Build Information
Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1540417
Build error leg or test failing: linux-x64 release CdacXPlatDumpGen — Fail on dump generation errors
Error Details
The runtime-diagnostics pipeline's cDAC cross-platform dump-generation stage (CdacXPlatDumpGen) fails at the final Fail on dump generation errors task across all legs (linux-x64, linux-arm, linux-arm64, windows-x64, windows-x86, windows-arm64). The individual createdump invocations for the debuggee crash scenarios succeed and write dumps, but the aggregating validation step reports failures and fails the job:
##[section]Starting: Fail on dump generation errors
Write-Error: One or more cDAC dump generation failures were detected. Failing the job.
##[error]PowerShell exited with code '1'.
##[section]Finishing: Fail on dump generation errors
The failure reproduces in the follow-up build (1542058), where all CdacXPlatDumpGen legs fail again, and is present in prior builds 1540417, 1537824, and 1537508. First observed after passing build 1538558.
Error Message
{
"ErrorMessage": "One or more cDAC dump generation failures were detected. Failing the job.",
"ErrorPattern": "",
"BuildRetry": false,
"ExcludeConsoleLog": false
}Note
Filed automatically by the CI outer-loop failure scanner (ci-failure-scan). This is an AI/Copilot-generated issue. Mitigation is tracked separately by the ci-failure-fix workflow.
Warning
Firewall blocked 1 domain
The following domain was blocked by the firewall during workflow execution:
awmgmcpg
To allow these domains, add them to the
network.allowedlist in your workflow frontmatter:
network:
allowed:
- defaults
- "awmgmcpg"See Network Configuration for more information.
Generated by CI Outer-Loop Failure Scanner · 756 AIC · ⌖ 17.3 AIC · ⊞ 18.3K · ◷
Report
| Build | Repository | Step Name | Console log | Pull Request |
|---|---|---|---|---|
| 1545665 | dotnet/runtime | Fail on dump generation errors | Log | |
| 1545580 | dotnet/runtime | Fail on dump generation errors | Log | #132043 |
| 1545259 | dotnet/runtime | Fail on dump generation errors | Log | |
| 1543796 | dotnet/runtime | Fail on dump generation errors | Log |
Summary
| 24-Hour Hit Count | 7-Day Hit Count | 1-Month Count |
|---|---|---|
| 2 | 4 | 4 |
Activity
dotnet-policy-service commentedon Aug 7, 2026
Tagging subscribers to this area: @steveisok, @tommcdon, @dotnet/dotnet-diag
See info in area-owners.md if you want to be subscribed.
github-actions commentedon Aug 8, 2026
Workflow artifact: ci-fix
Artifact kind: handoff
Linked KBE: #131979
Note
AI/Copilot-generated triage note.
This Known Build Error has no producible automated code change (reason: non-code/infra failure — a cross-platform dump-generation validation stage in the
runtime-diagnosticspipeline, not a single source defect I can safely correct), so I could not open even a best-effort PR. Looping in owners so it can be fixed forward rather than muted.Root cause (best analysis)
On
runtime-diagnostics, the cDAC cross-platform dump-generation stage (CdacXPlatDumpGen) fails at its final aggregating Fail on dump generation errors task across every leg (linux-x64, linux-arm, linux-arm64, windows-x64, windows-x86, windows-arm64):The individual
createdumpinvocations for the debuggee crash scenarios succeed and write dumps, but the aggregating validation step reports failures and fails the job. Because every leg (including both Linux and Windows) regresses simultaneously at the same aggregation task, this looks like a change in the validation harness / expected-output contract or a cDAC data-descriptor mismatch rather than a platform-specific dump defect. The failure first appears after passing build 1538558 and reproduces in 1540417, 1542058, 1537824, and 1537508 — a narrow regression window worth bisecting against changes to the cDAC dump-validation scripting and data descriptors.Evidence
CdacXPlatDumpGen— Fail on dump generation errors)Suggested reviewers / area contacts
area-Diagnostics-cdac):@steveisok,@tommcdon,@dotnet/dotnet-diagA fix would likely involve bisecting the ~1538558→1540417 window for a change to the cDAC dump-generation validation step or the data descriptors it relies on, then correcting the mismatch (or the validation's expectations) so the aggregating task passes again.
Warning
Firewall blocked 1 domain
The following domain was blocked by the firewall during workflow execution:
awmgmcpgSee Network Configuration for more information.
[cDAC] Disable Helix job monitor on XPlat dump generation (#132043)
[cDAC] Disable Helix job monitor on XPlat dump generation (dotnet#132043