Skip to content

Fix TensorPrimitives.IndexOfMaxMagnitude signed integer tie#128484

Merged
tannergooding merged 4 commits into
dotnet:mainfrom
lilinus:fix-indexofminmax
Jul 18, 2026
Merged

Fix TensorPrimitives.IndexOfMaxMagnitude signed integer tie#128484
tannergooding merged 4 commits into
dotnet:mainfrom
lilinus:fix-indexofminmax

Merge branch 'main' into fix-indexofminmax

65bd0cf
Select commit
Loading
Failed to load commit list.
Build Analysis / Helix Queue Insights (preview) succeeded Jul 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
runtime-dev-innerloop 51 minutes, 45 seconds 59 minutes, 44 seconds 1 hour, 7 minutes, 42 seconds
runtime 1 hour, 19 minutes, 10 seconds 2 hours, 31 minutes, 1 second 3 hours, 42 minutes, 52 seconds
dotnet-linker-tests 50 minutes 1 hour, 39 minutes, 51 seconds 2 hours, 29 minutes, 42 seconds

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 34 minutes, 15 seconds -0.76% 📉
windows.10.amd64.client.open.rt 33 minutes, 55 seconds 0.15% 📈
osx.15.amd64.open 29 minutes, 1 second 1.29% 📈
windows.10.amd64.serverrs5.open.rt 24 minutes, 38 seconds -0.23% 📉
windows.11.amd64.client.open.rt 24 minutes, 16 seconds -0.12% 📉

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