Skip to content

Remove unused runtime_config_t::m_prop_keys and m_prop_values

12a9ff3
Select commit
Loading
Failed to load commit list.
Open

Remove unused runtime_config_t::m_prop_keys and m_prop_values #128268

Remove unused runtime_config_t::m_prop_keys and m_prop_values
12a9ff3
Select commit
Loading
Failed to load commit list.
Build Analysis / Helix Queue Insights (preview) succeeded May 16, 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, 1 second 1 hour, 34 minutes, 20 seconds 2 hours, 20 minutes, 40 seconds
runtime-dev-innerloop 51 minutes, 38 seconds 57 minutes, 7 seconds 1 hour, 2 minutes, 36 seconds
runtime 1 hour, 23 minutes, 1 second 2 hours, 23 minutes, 31 seconds 3 hours, 24 minutes, 1 second

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, 1 minute, 52 seconds -0.17% 📉
windows.11.arm64.open 34 minutes, 5 seconds -0.09% 📉
windows.amd64.server2022.open.rt 32 minutes, 46 seconds 0.33% 📈
windows.server2025.amd64.open.rt 28 minutes, 30 seconds 0.14% 📈
windows.10.amd64.serverrs5.open.rt 24 minutes, 39 seconds -0.22% 📉

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