Add ASP.NET Core adversarial fix workflows - #68625
View the current status of Helix
Details
Pipeline Status
The list of queues is cached weekly. If your PR changes what queues your pipelines use, this information will not show the updated queues.
Estimated Pipeline Durations
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-ci | 49 minutes, 54 seconds | 1 hour, 15 minutes, 39 seconds | 1 hour, 41 minutes, 23 seconds |
| aspnetcore-always-green | ❌ | ❌ | ❌ |
| aspnetcore-components-e2e | 58 minutes, 31 seconds | 1 hour, 2 minutes, 50 seconds | 1 hour, 7 minutes, 9 seconds |
Pipelines denoted with ❌ means that this pipeline is highly variable, and we cannot predict its duration. This typically means this pipeline changes the legs it runs based on the PR's changed contents.
Highest Work Item Wait Time Queues
Here's a list of the top 3 queues with the highest work item wait time:
| Queue | Work Item Wait Time | Difference in Moving Avg |
|---|---|---|
| windows.amd64.vs2026.open | 55 minutes, 1 second | 0.39% 📈 |
| ubuntu.2404.amd64.open | 18 minutes, 48 seconds | -0.09% 📉 |
| osx.26.arm64.open | 20 seconds | -0.87% 📉 |
Grafana Dashboard
For more in-depth information on the status of Helix, visit our Grafana Dashboard.
Your Queues
☁️ Helix Queues
dotnet/aspnetcore is currently configured to submit to the following Helix queues:
🏢 On Premises Helix Queues
dotnet/aspnetcore uses the following on-prem queues:
Build Pools
Was this helpful?