[ci-scan-net11] MacCatalyst CoreCLR device tests canceled by Helix queue timeout — osx.15/osx.26 runners miss build deadline (net11.0)

[github-actions]

Summary

The Run DeviceTests MacCatalyst (CoreCLR) job in maui-pr-devicetests sends two parallel Helix jobs — one to osx.15.arm64.maui.open and one to osx.26.arm64.open. In ~5 out of every 10 builds, one of these queues stalls and the AzDO job exceeds its timeout (~1 hour), canceling the build task before all work items complete.

Build Information

• Pipeline: maui-pr-devicetests (ID 314)
• Build: 1473153 (latest failed)
• Branch: net11.0
• First seen: 2026-06-08 (build 1455190)
• Occurrences: 5 in last 10 builds (1455190, 1455596, 1455984, 1466211, 1470688, 1472847, 1473153 — with 1475417, 1471161, 1472464 succeeding)

Affected Legs

• DeviceTestsMacCatalyst_CoreCLR (Windows) — sends Helix jobs to osx.15.arm64.maui.open and osx.26.arm64.open
• Run DeviceTests MacCatalyst (CoreCLR) — parent task, canceled on queue timeout

Error Message

# Build 1473153 — osx.26.arm64.open stalled:
Starting Azure Pipelines Test Run DeviceTestsMacCatalyst_CoreCLR_osx.26.arm64.open_Release_CoreCLR
Sent Helix Job; see work items at https://helix.dot.net/api/jobs/<id>/workitems
Sending Job to osx.26.arm64.open...
Waiting for completion of job <id> on osx.15.arm64.maui.open
Waiting for completion of job <id> on osx.26.arm64.open
##[error]The Operation will be canceled. The next steps may not contain expected logs.
error : Build task was cancelled while waiting on job '<id>'. Attempting to cancel this job in Helix...
##[error]The operation was canceled.

# Build 1455190 — osx.15.arm64.maui.open stalled (~58 min wait):
Job <id> on osx.26.arm64.open is completed with 7 finished work items.
##[error]The Operation will be canceled. The next steps may not contain expected logs.
error : Build task was cancelled while waiting on job '<id>'. Attempting to cancel this job in Helix...

Recommended Action

1. Check Helix queue health for osx.15.arm64.maui.open and osx.26.arm64.open — the queues have been intermittently saturated since June 8. The ~58-minute wait on the longer-running queue matches typical queue exhaustion when macOS agents are fully occupied.
2. Check whether macOS tests can be split or parallelized differently — the two-queue split causes the entire job to wait for the slower queue. Consider whether tests can be better balanced, or whether a job timeout extension is needed.
3. Contact dnceng if agent capacity on osx.15.arm64.maui.open / osx.26.arm64.open is insufficient — capacity issues on shared Helix queues require infrastructure-team intervention.
4. Verify with 1475417 — the most recent build succeeded, suggesting this may be intermittent queue saturation rather than a configuration error.

Generated by CI Failure Scanner (net11.0) · 2.5K AIC · ⌖ 13.3 AIC · ⊞ 34.3K · ◷

[SubhikshaSf4851]

I checked the latest CI run in one of the PRs and confirmed that the test category DeviceTests MacCatalyst and DeviceTests MacCatalyst, completed successfully on the Windows and Mac platform