Skip to content

Comment out a couple tests and add notes. Needs test and cleanup.

Build Analysis / Helix Queue Insights (preview) succeeded Jul 25, 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
dotnet-linker-tests 42 minutes, 37 seconds 1 hour, 17 seconds 1 hour, 17 minutes, 57 seconds
runtime-dev-innerloop 33 minutes, 35 seconds 54 minutes, 47 seconds 1 hour, 16 minutes
runtime 59 minutes, 22 seconds 1 hour, 48 minutes, 54 seconds 2 hours, 38 minutes, 26 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.serverrs5.open.rt 55 minutes, 39 seconds -0.38% 📉
ubuntu.2004.armarch.open 38 minutes, 52 seconds -0.43% 📉
windows.amd64.server2022.open.rt 37 minutes, 42 seconds -0.02% 📉
windows.11.amd64.client.open.rt 31 minutes -0.08% 📉
ubuntu.2204.amd64.open.rt 30 minutes, 35 seconds -0.71% 📉

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