Skip to content

Skip MatchesCodesignOutput test similar to upstream

d3dfcee
Select commit
Loading
Failed to load commit list.
Merged

[release/10] Bump MacOS helix queues to latest #122990

Skip MatchesCodesignOutput test similar to upstream
d3dfcee
Select commit
Loading
Failed to load commit list.
Build Analysis / Helix Queue Insights (preview) succeeded Jan 12, 2026 in 0s

View the current status of Helix

Details

Pipeline Status

The list of queues is cached weekly. If your PR changes what queues your pipelines use, this information will not show the updated queues.

Estimated Pipeline Durations

This model assumes that the current state of the entire CI infrastructure is normal, and that your CI pipelines will succeed.

Pipeline Lower Bound Estimated Time Upper Bound
runtime-dev-innerloop 48 minutes, 42 seconds 58 minutes, 36 seconds 1 hour, 8 minutes, 29 seconds
dotnet-linker-tests 56 minutes, 14 seconds 1 hour, 15 minutes, 59 seconds 1 hour, 35 minutes, 43 seconds
runtime 49 minutes, 49 seconds 1 hour, 59 minutes, 10 seconds 3 hours, 8 minutes, 31 seconds

Highest Work Item Wait Time Queues

Here's a list of the top 5 queues with the highest work item wait time:

Queue Work Item Wait Time Difference in Moving Avg
ubuntu.2204.amd64.open.svc 29 minutes, 16 seconds -0.28% 📉
azurelinux.3.arm64.open 28 minutes, 19 seconds -0.42% 📉
windows.10.amd64.open.svc 22 minutes, 8 seconds -0.14% 📉
azurelinux.3.amd64.open.svc 17 minutes, 28 seconds -0.48% 📉
windows.11.arm64.open 17 minutes, 5 seconds -0.43% 📉

Grafana Dashboard

For more in-depth information on the status of Helix, visit our Grafana Dashboard.

Your Queues

☁️ Helix Queues

dotnet/runtime is currently configured to submit to the following Helix queues:

🏢 On Premises Helix Queues

dotnet/runtime uses the following on-prem queues:

⚠️ We failed to query some work item wait times.

This typically means there hasn't been any recent work submitted to these queues. If this looks wrong, please contact @dnceng.

Build Pools

Was this helpful? Yes No