Skip to content

Fix the IOCP count config var test

Build Analysis / Helix Queue Insights (preview) succeeded Aug 14, 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 35 minutes, 29 seconds 53 minutes, 35 seconds 1 hour, 11 minutes, 41 seconds
dotnet-linker-tests 43 minutes, 5 seconds 59 minutes, 36 seconds 1 hour, 16 minutes, 8 seconds
runtime 58 minutes, 20 seconds 1 hour, 47 minutes, 19 seconds 2 hours, 36 minutes, 18 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.2004.armarch.open 38 minutes, 59 seconds -0.26% 📉
windows.11.arm64.open 37 minutes, 17 seconds -0.13% 📉
ubuntu.2204.amd64.open.rt 30 minutes, 14 seconds -0.03% 📉
windows.amd64.server2022.open.rt 27 minutes, 31 seconds -0.33% 📉
windows.81.amd64.open.rt 26 minutes, 15 seconds -0.07% 📉

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