Implement SocketsHttpHandler.InitialHttp2MaxConcurrentStreams by MihaZupan · Pull Request #132521 · 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	53 minutes, 49 seconds	1 hour, 1 minute, 55 seconds	1 hour, 10 minutes
dotnet-linker-tests	48 minutes, 32 seconds	1 hour, 33 minutes, 21 seconds	2 hours, 18 minutes, 10 seconds
runtime	1 hour, 16 minutes, 3 seconds	2 hours, 33 minutes, 34 seconds	3 hours, 51 minutes, 5 seconds
runtime-libraries enterprise-linux	36 minutes, 22 seconds	37 minutes, 52 seconds	39 minutes, 22 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:

_{Was this helpful?}