Skip to content

Assert that time_t is 64-bit

Build Analysis / Helix Queue Insights (preview) succeeded Apr 26, 2024 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 28 minutes, 10 seconds 58 minutes, 13 seconds 1 hour, 28 minutes, 16 seconds
dotnet-linker-tests 38 minutes, 41 seconds 59 minutes, 27 seconds 1 hour, 20 minutes, 13 seconds
runtime 59 minutes, 57 seconds 1 hour, 46 minutes, 58 seconds 2 hours, 34 minutes

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 52 minutes, 15 seconds 0.02% 📈
windows.10.amd64.serverrs5.open.rt 27 minutes, 11 seconds -0.18% 📉
windows.81.amd64.open.rt 26 minutes, 36 seconds -0.25% 📉
windows.11.amd64.client.open.rt 26 minutes, 34 seconds -0.17% 📉
ubuntu.2004.armarch.open 24 minutes, 24 seconds -0.17% 📉

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

Microsoft Hosted

This pipeline will build on the following Microsoft Hosted build pools:

Click here for information about these agents.

  • ubuntu-22.04
  • ubuntu-latest
  • macOS-latest
  • macOS-12

Was this helpful? Yes No

View more details on Build Analysis