Skip to content

Fix CI flakiness: 5 root causes addressing 48% failure rate

189c634
Select commit
Loading
Failed to load commit list.
Open

Fix CI flakiness: MSB4216 task host failures, dotnet-watch hangs, NuGet errors #53424

Fix CI flakiness: 5 root causes addressing 48% failure rate
189c634
Select commit
Loading
Failed to load commit list.
Build Analysis / Helix Queue Insights (preview) succeeded Mar 15, 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-sdk-public-ci 46 minutes, 3 seconds 1 hour, 17 minutes, 7 seconds 1 hour, 48 minutes, 11 seconds

Highest Work Item Wait Time Queues

Here's a list of the top 4 queues with the highest work item wait time:

Queue Work Item Wait Time Difference in Moving Avg
windows.amd64.vs2026.pre.scout.open 33 minutes, 12 seconds -0.05% 📉
ubuntu.2204.amd64.open 32 minutes, 28 seconds -0.3% 📉
osx.15.amd64.open 5 minutes, 9 seconds -0.55% 📉
osx.15.arm64.open 2 minutes, 1 second -0.4% 📉

Grafana Dashboard

For more in-depth information on the status of Helix, visit our Grafana Dashboard.

Your Queues

☁️ Helix Queues

dotnet/sdk is currently configured to submit to the following Helix queues:

🏢 On Premises Helix Queues

dotnet/sdk uses the following on-prem queues:

Build Pools

Was this helpful? Yes No