Skip to content

[mono] Fix interface call in case of reabstraction - #131219

Open
BrzVlad wants to merge 2 commits into
dotnet:mainfrom
BrzVlad:fix-mono-dim-reabstraction
Open

[mono] Fix interface call in case of reabstraction#131219
BrzVlad wants to merge 2 commits into
dotnet:mainfrom
BrzVlad:fix-mono-dim-reabstraction

add test

8e751a7
Select commit
Loading
Failed to load commit list.
Build Analysis / Helix Queue Insights (preview) succeeded Jul 27, 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
runtime-dev-innerloop 52 minutes, 31 seconds 1 hour, 52 seconds 1 hour, 9 minutes, 13 seconds
dotnet-linker-tests 49 minutes, 54 seconds 1 hour, 36 minutes, 19 seconds 2 hours, 22 minutes, 44 seconds
runtime 1 hour, 20 minutes, 42 seconds 2 hours, 34 minutes, 54 seconds 3 hours, 49 minutes, 7 seconds

Highest Work Item Wait Time Queues

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

Queue Work Item Wait Time Difference in Moving Avg
windows.10.amd64.serverrs5.open.rt 23 minutes, 13 seconds -0.59% 📉
windows.server2025.amd64.open.rt 22 minutes, 11 seconds -0.53% 📉
osx.15.amd64.iphone.open 18 minutes, 37 seconds -0.53% 📉
windows.10.amd64.open.rt 17 minutes, 44 seconds -0.84% 📉
windows.11.arm64.open 10 minutes, 2 seconds -0.66% 📉

Grafana Dashboard

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

Your Queues

☁️ Helix Queues

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

🏢 On Premises Helix Queues

dotnet/runtime uses the following on-prem queues:

Build Pools

Was this helpful? Yes No