Skip to content

Merging internal commits for release/9.0#65381

Merged
wtgodbe merged 14 commits into
dotnet:release/9.0from
vseanreesermsft:internal-merge-9.0-2026-02-10-1049
Feb 10, 2026
Merged

Merging internal commits for release/9.0#65381
wtgodbe merged 14 commits into
dotnet:release/9.0from
vseanreesermsft:internal-merge-9.0-2026-02-10-1049

Merge commit '087328de5f1e0067be48d87295ae8d92064a1535' into internal…

ce97af7
Select commit
Loading
Failed to load commit list.
Build Analysis / Helix Queue Insights (preview) succeeded Feb 11, 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-ci 39 minutes, 18 seconds 1 hour, 10 minutes, 39 seconds 1 hour, 41 minutes, 59 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
osx.15.amd64.open 1 hour, 11 minutes, 39 seconds -0.11% 📉
ubuntu.2204.amd64.open.svc 34 minutes, 24 seconds -0.06% 📉
windows.amd64.vs2022.pre.open.svc 24 minutes, 56 seconds -0.27% 📉
windows.11.amd64.client.open.svc 22 minutes, 49 seconds -0.27% 📉

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