Skip to content

Fix warning when using nullable properties in ValidationMessageStore.Add field accessor#66901

Open
BharatRamsf3693 wants to merge 26 commits into
dotnet:mainfrom
BharatRamsf3693:main
Open

Fix warning when using nullable properties in ValidationMessageStore.Add field accessor#66901
BharatRamsf3693 wants to merge 26 commits into
dotnet:mainfrom
BharatRamsf3693:main

Merge branch 'dotnet:main' into main

9109815
Select commit
Loading
Failed to load commit list.
Build Analysis / Helix Queue Insights (preview) succeeded Jul 12, 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 1 hour, 5 seconds 1 hour, 3 minutes, 34 seconds 1 hour, 7 minutes, 4 seconds
aspnetcore-ci 45 minutes, 26 seconds 1 hour, 12 minutes, 37 seconds 1 hour, 39 minutes, 48 seconds
aspnetcore-template-tests-pr 1 hour, 22 minutes, 18 seconds 1 hour, 36 minutes, 9 seconds 1 hour, 50 minutes

Highest Work Item Wait Time Queues

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

Queue Work Item Wait Time Difference in Moving Avg
osx.26.arm64.open 22 seconds -0.92% 📉

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:

⚠️ We failed to query some work item wait times.

This typically means there hasn't been any recent work submitted to these queues. If this looks wrong, please contact @dnceng.

Build Pools

Was this helpful? Yes No

View more details on Build Analysis