[Blazor] Propagate SignalR authentication refresh to server circuits by kotlarmilos · Pull Request #68221 · dotnet/aspnetcore

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
aspnetcore-components-e2e	59 minutes, 40 seconds	1 hour, 3 minutes, 5 seconds	1 hour, 6 minutes, 29 seconds
aspnetcore-template-tests-pr	1 hour, 21 minutes, 50 seconds	1 hour, 35 minutes, 3 seconds	1 hour, 48 minutes, 16 seconds
aspnetcore-ci	47 minutes	1 hour, 14 minutes, 12 seconds	1 hour, 41 minutes, 25 seconds

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

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

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

dotnet/aspnetcore uses the following on-prem queues:

_{Was this helpful?}