JIT: Fix infinite loop in copy prop GT_COMMA update logic #105196

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
dotnet-linker-tests	42 minutes, 35 seconds	1 hour, 26 seconds	1 hour, 18 minutes, 17 seconds
runtime-dev-innerloop	33 minutes, 26 seconds	54 minutes, 58 seconds	1 hour, 16 minutes, 30 seconds
runtime	1 hour, 2 seconds	1 hour, 49 minutes, 19 seconds	2 hours, 38 minutes, 35 seconds
runtime-coreclr superpmi-replay	1 hour, 8 minutes, 8 seconds	2 hours, 42 minutes, 39 seconds	4 hours, 17 minutes, 11 seconds
runtime-coreclr superpmi-diffs	50 minutes, 21 seconds	2 hours, 25 minutes	3 hours, 59 minutes, 38 seconds

Here's a list of the top 5 queues with the highest work item wait time:

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:

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

This pipeline will build on the following Microsoft Hosted build pools:

Click here for information about these agents.

_{Was this helpful?}