You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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:
Pool/queue unavailability for Windows.11.Arm64.Open
Conditional step evaluation removing all steps due to a configuration mismatch
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.
#125901search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#122311search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#114055search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#120891search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#84006search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#112841search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#83317search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#51317search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#86416search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#90084search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#77241search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#115319search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#93768search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#96506search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#90803search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#126682search_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:
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
Errors log
The Phase log shows template evaluation completing with
steps: []— no actual work is scheduled: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:
Windows.11.Arm64.OpenThis 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.
search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".To allow these resources, lower
min-integrityin your GitHub frontmatter: