Skip to content

[tests] Add more logging to pinpoint hang

Build Analysis / Helix Queue Insights (preview) succeeded Jul 16, 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, 21 seconds 1 hour, 30 seconds 1 hour, 18 minutes, 38 seconds
runtime-dev-innerloop 32 minutes, 47 seconds 55 minutes, 4 seconds 1 hour, 17 minutes, 20 seconds
runtime 58 minutes, 52 seconds 1 hour, 48 minutes, 47 seconds 2 hours, 38 minutes, 42 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.rt 2 hours, 39 minutes, 59 seconds 0.35% πŸ“ˆ
windows.10.amd64.open.rt 2 hours, 26 minutes, 6 seconds 0.15% πŸ“ˆ
osx.13.amd64.appletv.open 34 minutes, 51 seconds -0.27% πŸ“‰
windows.amd64.server2022.open.rt 33 minutes, 21 seconds -0.33% πŸ“‰
ubuntu.2004.armarch.open 32 minutes, 2 seconds -0.42% πŸ“‰

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

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