Skip to content

[RyuJit] Add VisitOperandUses - #125073

Merged
AndyAyersMS merged 1 commit into
dotnet:mainfrom
SingleAccretion:VisitUses
Mar 3, 2026
Merged

[RyuJit] Add VisitOperandUses#125073
AndyAyersMS merged 1 commit into
dotnet:mainfrom
SingleAccretion:VisitUses

VisitUses

1243b79
Select commit
Loading
Failed to load commit list.
Build Analysis / Helix Queue Insights (preview) succeeded Mar 3, 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.

PipelineLower BoundEstimated TimeUpper Bound
dotnet-linker-tests52 minutes, 13 seconds1 hour, 22 minutes, 51 seconds1 hour, 53 minutes, 28 seconds
runtime-coreclr hardware-intrinsics1 hour, 9 minutes, 4 seconds1 hour, 47 minutes, 3 seconds2 hours, 25 minutes, 2 seconds
runtime-dev-innerloop50 minutes, 10 seconds55 minutes, 32 seconds1 hour, 54 seconds
runtime-coreclr superpmi-diffs
runtime1 hour, 25 minutes2 hours, 12 minutes, 26 seconds2 hours, 59 minutes, 52 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:

QueueWork Item Wait TimeDifference in Moving Avg
windows.amd64.server2022.open.rt52 minutes, 48 seconds-0.06% 📉
azurelinux.3.arm64.open41 minutes, 32 seconds-0.16% 📉
windows.10.amd64.open.rt32 minutes, 42 seconds-0.27% 📉
ubuntu.2204.amd64.android.29.open.rt32 minutes, 12 seconds-0.4% 📉
windows.11.amd64.client.open.rt32 minutes, 3 seconds-0.18% 📉

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? YesNo