JIT: fix stress issue with profile consistency #101259

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	26 minutes, 54 seconds	57 minutes, 30 seconds	1 hour, 28 minutes, 6 seconds
dotnet-linker-tests	37 minutes, 49 seconds	58 minutes, 22 seconds	1 hour, 18 minutes, 55 seconds
runtime	56 minutes, 38 seconds	1 hour, 44 minutes, 47 seconds	2 hours, 32 minutes, 55 seconds
runtime-coreclr superpmi-diffs	1 hour, 21 minutes, 29 seconds	2 hours, 17 minutes, 22 seconds	3 hours, 13 minutes, 15 seconds
runtime-coreclr superpmi-replay	1 hour, 36 minutes, 56 seconds	2 hours, 44 minutes, 44 seconds	3 hours, 52 minutes, 33 seconds
runtime-coreclr libraries-jitstress	39 minutes, 22 seconds	1 hour, 24 minutes, 4 seconds	2 hours, 8 minutes, 47 seconds
runtime-coreclr jitstress	1 hour, 44 minutes, 50 seconds	2 hours, 49 minutes, 5 seconds	3 hours, 53 minutes, 20 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?}