Skip to content

Apply suggestion from @bartonjs

450eb5c
Select commit
Loading
Failed to load commit list.
Merged

Add an in-memory cache for CRLs on Linux #123562

Apply suggestion from @bartonjs
450eb5c
Select commit
Loading
Failed to load commit list.
Build Analysis / Helix Queue Insights (preview) succeeded Feb 11, 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
dotnet-linker-tests 52 minutes, 48 seconds 1 hour, 19 minutes, 16 seconds 1 hour, 45 minutes, 44 seconds
runtime-dev-innerloop 49 minutes, 55 seconds 55 minutes, 24 seconds 1 hour, 53 seconds
runtime 1 hour, 24 minutes, 2 seconds 2 hours, 10 minutes, 37 seconds 2 hours, 57 minutes, 12 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
windows.10.amd64.open.rt 1 hour, 5 minutes, 10 seconds 0.5% 📈
azurelinux.3.arm64.open 1 hour, 18 seconds 0.18% 📈
windows.11.arm64.open 47 minutes, 20 seconds 0.37% 📈
azurelinux.3.amd64.open.rt 46 minutes, 21 seconds 0.06% 📈
windows.11.amd64.client.open.rt 40 minutes, 49 seconds 0.08% 📈

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:

Build Pools

Was this helpful? Yes No