Skip to content

Merge branch 'main' into jit-wb-preserve-fp

7fead2b
Select commit
Loading
Failed to load commit list.
Merged

JIT: don't kill FP/SIMD/mask regs across x64 write barriers #128778

Merge branch 'main' into jit-wb-preserve-fp
7fead2b
Select commit
Loading
Failed to load commit list.
Build Analysis / Helix Queue Insights (preview) succeeded May 30, 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
runtime-dev-innerloop 51 minutes, 29 seconds 57 minutes, 31 seconds 1 hour, 3 minutes, 33 seconds
dotnet-linker-tests 48 minutes, 42 seconds 1 hour, 38 minutes, 4 seconds 2 hours, 27 minutes, 26 seconds
runtime-coreclr superpmi-diffs
runtime 1 hour, 23 minutes, 22 seconds 2 hours, 24 minutes, 3 seconds 3 hours, 24 minutes, 43 seconds
runtime-coreclr hardware-intrinsics 1 hour, 11 minutes, 37 seconds 1 hour, 58 minutes, 5 seconds 2 hours, 44 minutes, 33 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.10.amd64.open.rt 2 hours, 15 minutes, 19 seconds -0.06% 📉
osx.15.amd64.open 42 minutes, 54 seconds -0.78% 📉
windows.11.amd64.android-armel.open 34 minutes, 58 seconds -0.7% 📉
windows.11.arm64.open 26 minutes, 19 seconds -0.64% 📉
osx.15.amd64.iphone.open 16 minutes, 42 seconds -0.75% 📉

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:

⚠️ We failed to query some work item wait times.

This typically means there hasn't been any recent work submitted to these queues. If this looks wrong, please contact @dnceng.

Build Pools

Was this helpful? Yes No