Skip to content

Address code review comments

c49fd79
Select commit
Loading
Failed to load commit list.
Merged

Implement UnknownSizeFrame for locals with unknown size #125491

Address code review comments
c49fd79
Select commit
Loading
Failed to load commit list.
Build Analysis / Helix Queue Insights (preview) succeeded May 7, 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-linker-tests 48 minutes, 30 seconds 1 hour, 32 minutes, 55 seconds 2 hours, 17 minutes, 21 seconds
runtime-coreclr hardware-intrinsics 1 hour, 8 minutes, 49 seconds 1 hour, 52 minutes, 59 seconds 2 hours, 37 minutes, 9 seconds
runtime-dev-innerloop 51 minutes, 52 seconds 57 minutes, 13 seconds 1 hour, 2 minutes, 33 seconds
runtime-coreclr superpmi-diffs
runtime-coreclr superpmi-replay
runtime 1 hour, 23 minutes, 51 seconds 2 hours, 22 minutes, 45 seconds 3 hours, 21 minutes, 40 seconds

Pipelines denoted with ❌ means that this pipeline is highly variable, and we cannot predict its duration. This typically means this pipeline changes the legs it runs based on the PR's changed contents.

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
windows.11.amd64.client.open.rt 56 minutes, 32 seconds 0.6% 📈
windows.10.amd64.open.rt 39 minutes, 14 seconds -0.29% 📉
azurelinux.3.arm64.open 31 minutes, 36 seconds 0.29% 📈
windows.10.amd64.serverrs5.open.rt 28 minutes, 58 seconds 0.04% 📈
windows.amd64.server2022.open.rt 27 minutes, 16 seconds 0% 📈

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:

Build Pools

Was this helpful? Yes No