Skip to content

Unquarantine WebWorker E2E tests and add diagnostics#66072

Merged
ilonatommy merged 4 commits into
dotnet:mainfrom
ilonatommy:itomkowicz/unquarantine-webworker-tests
Apr 2, 2026
Merged

Unquarantine WebWorker E2E tests and add diagnostics#66072
ilonatommy merged 4 commits into
dotnet:mainfrom
ilonatommy:itomkowicz/unquarantine-webworker-tests

Merge branch 'main' into itomkowicz/unquarantine-webworker-tests

02c4aff
Select commit
Loading
Failed to load commit list.
Build Analysis / Helix Queue Insights (preview) succeeded Apr 1, 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
aspnetcore-template-tests-pr 1 hour, 22 minutes, 55 seconds 1 hour, 36 minutes, 35 seconds 1 hour, 50 minutes, 16 seconds
aspnetcore-ci 40 minutes, 44 seconds 1 hour, 5 minutes, 38 seconds 1 hour, 30 minutes, 32 seconds

Highest Work Item Wait Time Queues

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

Queue Work Item Wait Time Difference in Moving Avg
windows.amd64.vs2026.pre.scout.open 23 minutes, 55 seconds -0.4% 📉
ubuntu.2204.amd64.open 15 minutes, 36 seconds -0.56% 📉
osx.15.amd64.open 12 minutes, 42 seconds -0.29% 📉

Grafana Dashboard

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

Your Queues

☁️ Helix Queues

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

🏢 On Premises Helix Queues

dotnet/aspnetcore 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

Was this helpful? Yes No