Skip to content

Merging internal commits for release/8.0.1xx#52432

Merged
vseanreesermsft merged 39 commits into
dotnet:release/8.0.1xxfrom
vseanreesermsft:internal-merge-8.0.1xx-2026-01-13-1151
Jan 18, 2026
Merged

Merging internal commits for release/8.0.1xx#52432
vseanreesermsft merged 39 commits into
dotnet:release/8.0.1xxfrom
vseanreesermsft:internal-merge-8.0.1xx-2026-01-13-1151

Disable workload resolver tests on Full Framework for 8.0

6f9b68e
Select commit
Loading
Failed to load commit list.
Build Analysis / Helix Queue Insights (preview) succeeded Jan 18, 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 53 minutes, 44 seconds 1 hour, 33 minutes 2 hours, 12 minutes, 16 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
ubuntu.2204.amd64.open.svc 43 minutes, 10 seconds 0.3% 📈
windows.amd64.vs2022.pre.open.svc 26 minutes, 48 seconds -0.01% 📉
osx.15.amd64.open 8 minutes, 25 seconds -0.51% 📉

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

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
  • windows-2022
  • windows-latest
  • windows-2019

Was this helpful? Yes No