Skip to content

[ci-scan] Build break: windows-arm64 checked phase produces empty steps across jitstress pipelines #127987

@github-actions

Description

@github-actions

Caution

Security scanning requires review for CI Outer-Loop Failure Scanner

Details

The threat detection results could not be parsed. The workflow output should be reviewed before merging.

Review the workflow run logs for details.

Reasoning

Multiple JIT stress pipelines have a recurring windows-arm64 checked Phase failure where the Phase completes with steps: [] (empty steps array). No Job is created underneath the Phase, so no tests run. This appears to be a pipeline configuration or pool issue, not a test failure.

Impact on platforms

  • runtime-coreclr jitstress2-jitstressregs (def 111) + windows-arm64 checked + build 1406635 (2026-05-03)
  • runtime-coreclr gcstress0x3-gcstress0xc (def 112) + windows-arm64 checked + build 1406540 (2026-05-03)
  • runtime-coreclr jitstress-isas-arm (def 116) + windows-arm64 checked + build 1406275 (2026-05-02)
  • runtime-coreclr r2r (def 120) + windows x86 + linux arm64 + build 1413284 (2026-05-07)
  • runtime-coreclr crossgen2 (def 124) + windows-arm64 checked + build 1413322 (2026-05-07)

Errors log

The Phase log shows template evaluation completing with steps: [] — no actual work is scheduled:

Template and static variable resolution complete. Final runtime YAML document:
steps: []

First build it occurred

Present in builds from 2026-05-02 through 2026-05-08 across 5 different pipeline definitions. This is computed within the scanned window and may not be the true origin.

Recommended action

Investigate why the windows-arm64 checked Phase resolves to empty steps. Possible causes:

  1. Pool/queue unavailability for Windows.11.Arm64.Open
  2. Conditional step evaluation removing all steps due to a configuration mismatch
  3. YAML template parameter issue specific to the windows-arm64 checked configuration

This is an infrastructure issue — no KBE is appropriate since Build Analysis does not cover build breaks.

Note

🔒 Integrity filter blocked 19 items

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

  • #125901 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #122311 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #114055 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #120891 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #84006 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #112841 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #83317 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #51317 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #86416 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #90084 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #77241 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #115319 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #93768 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #96506 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #90803 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #126682 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • ... and 3 more items

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 · ● 35.9M ·

Metadata

Metadata

Assignees

No one assigned

    Labels

    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