Skip to content

[release/11.0-rc1] Force runtime discovery for TypeMap entries when unable to encode a type in crossgen2's precomputed TypeMap - #132984

Open
jtschuster wants to merge 1 commit into
dotnet:release/11.0-rc1from
jtschuster:guard-typemap-emission
Open

[release/11.0-rc1] Force runtime discovery for TypeMap entries when unable to encode a type in crossgen2's precomputed TypeMap#132984
jtschuster wants to merge 1 commit into
dotnet:release/11.0-rc1from
jtschuster:guard-typemap-emission

Force runtime discover for TypeMapEntry when unable to encode a type

13c98ac
Select commit
Loading
Failed to load commit list.
Build Analysis / Helix Queue Insights (preview) succeeded Aug 31, 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 53 minutes, 12 seconds 1 hour, 4 minutes, 1 second 1 hour, 14 minutes, 49 seconds
dotnet-linker-tests 1 hour, 1 minute, 43 seconds 1 hour, 12 minutes, 13 seconds 1 hour, 22 minutes, 43 seconds

😕 dotnet/runtime doesn't use any Helix Queues.

This GitHub check is meant to show insights into the status of Helix as configured for this Repository.

We couldn't find any queues that this repository uses. If this seems wrong, please ensure that your pipeline is configured under dnceng's AzDo orginization under the public project. Please contact @dnceng for more assistance.

Grafana Dashboard

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

Build Pools

Was this helpful? Yes No