Skip to content

Add ToUpperOrdinal and ToLowerOrdinal casing APIs#130140

Open
tarekgh wants to merge 12 commits into
dotnet:mainfrom
tarekgh:ordinal-casing-apis
Open

Add ToUpperOrdinal and ToLowerOrdinal casing APIs#130140
tarekgh wants to merge 12 commits into
dotnet:mainfrom
tarekgh:ordinal-casing-apis

Remove unused using in String.Manipulation.cs

6752db1
Select commit
Loading
Failed to load commit list.
Build Analysis / Helix Queue Insights (preview) succeeded Jul 9, 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, 48 seconds 59 minutes, 48 seconds 1 hour, 7 minutes, 49 seconds
runtime 1 hour, 19 minutes, 38 seconds 2 hours, 31 minutes, 41 seconds 3 hours, 43 minutes, 45 seconds
dotnet-linker-tests 49 minutes, 56 seconds 1 hour, 39 minutes, 26 seconds 2 hours, 28 minutes, 55 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 5 hours, 46 minutes, 10 seconds 0.01% 📈
azurelinux.3.arm64.open 1 hour, 33 minutes, 4 seconds 0.17% 📈
windows.10.amd64.serverrs5.open.rt 25 minutes -0.12% 📉
windows.10.amd64.client.open.rt 20 minutes, 59 seconds -0.38% 📉
azurelinux.3.amd64.open.rt 17 minutes, 43 seconds 0.23% 📈

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