Skip to content

[ci-scan] Hang: cDAC dump generation on Windows.11.Arm64.Open #129384

@github-actions

Description

@github-actions

Build Information

Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1462610
Build error leg or test failing: windows-arm64 release CdacXPlatDumpGen - CdacDumpGen

Error Details

The cDAC dump generation Helix work item (CdacDumpGen) hangs on the Windows.11.Arm64.Open queue until the AzDO pipeline timeout kills it (~2 hours). The Helix job exits with code -1234 (timeout/killed). After cancellation, the "Fail on dump generation errors" PowerShell task detects the incomplete run and fails the job.

Sent Helix Job; see work items at https://helix.dot.net/api/jobs/cbc4a706-66da-4907-8f60-2e028b7d47de/workitems?api-version=2019-06-17
Waiting for completion of job cbc4a706-66da-4907-8f60-2e028b7d47de on Windows.11.Arm64.Open
##[error]The Operation will be canceled. The next steps may not contain expected logs.
Build task was cancelled while waiting on job 'cbc4a706-66da-4907-8f60-2e028b7d47de'. Attempting to cancel this job in Helix...
##[error]The operation was canceled.
One or more cDAC dump generation failures were detected. Failing the job.

Error Message

true only for clear infra flakes. ExcludeConsoleLog skips helix log scanning. -->

{
  "ErrorMessage": "One or more cDAC dump generation failures were detected. Failing the job.",
  "ErrorPattern": "",
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}

Impact on platforms

  • runtime-diagnostics (def 309) / windows-arm64 release CdacXPlatDumpGen / Helix queue: Windows.11.Arm64.Open / exit code: -1234 (timeout)

First build it occurred

Confirmed in follow-up build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1463142 (same CdacDumpGen timeout on Windows.11.Arm64.Open)

Duplicate search

No existing KBE or PR matches this signature.


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

🔒 Integrity filter blocked 4 items

The following items were blocked because they don't meet the GitHub integrity level.

  • #124417 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #125436 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #125670 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #90312 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".

To allow these resources, lower min-integrity in your GitHub frontmatter:

tools:
  github:
    min-integrity: approved  # merged | approved | unapproved | none

Generated by CI Outer-Loop Failure Scanner · ● 72.4M ·

Report

Summary

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    Known Build ErrorUse this to report build issues in the .NET Helix tabagentic-workflowsblocking-clean-ciBlocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'untriagedNew issue has not been triaged by the area owner

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions