[release/9.0-staging] JIT: fix bug in loop cloning with down-counting loops by github-actions[bot] · Pull Request #126913 · dotnet/runtime

View the current status of Helix

The list of queues is cached weekly. If your PR changes what queues your pipelines use, this information will not show the updated queues.

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	41 minutes, 45 seconds	1 hour, 4 seconds	1 hour, 18 minutes, 23 seconds
dotnet-linker-tests	41 minutes, 23 seconds	1 hour, 25 minutes, 34 seconds	2 hours, 9 minutes, 46 seconds

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.svc	42 minutes, 3 seconds	0.2% 📈
windows.amd64.server2022.open.svc	41 minutes, 42 seconds	-0.55% 📉
osx.15.amd64.open	41 minutes, 23 seconds	0.1% 📈
azurelinux.3.amd64.open.svc	41 minutes, 6 seconds	0.11% 📈
windows.10.amd64.serverrs5.open.svc	38 minutes, 14 seconds	-0.02% 📉

For more in-depth information on the status of Helix, visit our Grafana Dashboard.

dotnet/runtime is currently configured to submit to the following Helix queues:

dotnet/runtime uses the following on-prem queues:

_{Was this helpful?}