Fix trim/AOT safety for custom event argument deserialization in Blazor - #68113
Draft
NanthiniMahalingam wants to merge 2 commits into
Draft
Fix trim/AOT safety for custom event argument deserialization in Blazor#68113NanthiniMahalingam wants to merge 2 commits into
NanthiniMahalingam wants to merge 2 commits into
Build Analysis / Helix Queue Insights (preview)
succeeded
Jul 30, 2026 in 0s
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-components-e2e | 59 minutes, 55 seconds | 1 hour, 3 minutes, 19 seconds | 1 hour, 6 minutes, 44 seconds |
| aspnetcore-ci | 46 minutes, 10 seconds | 1 hour, 13 minutes, 53 seconds | 1 hour, 41 minutes, 37 seconds |
| aspnetcore-template-tests-pr | 1 hour, 21 minutes, 58 seconds | 1 hour, 35 minutes, 14 seconds | 1 hour, 48 minutes, 30 seconds |
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 |
|---|---|---|
| ubuntu.2404.amd64.open | 12 minutes, 58 seconds | -0.07% 📉 |
| windows.amd64.vs2026.open | 5 minutes, 18 seconds | -0.73% 📉 |
| osx.26.arm64.open | 59 seconds | 0.44% 📈 |
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:
- ubuntu.2404.amd64.open
- ubuntu.2404.amd64.open
- ubuntu.2404.amd64.open
- windows.amd64.vs2026.open
- windows.amd64.vs2026.open
- windows.amd64.vs2026.open
🏢 On Premises Helix Queues
dotnet/aspnetcore uses the following on-prem queues:
Build Pools
Was this helpful?
Loading