[TrimmableTypeMap] Resolve all TrimmableIgnore, SSL, and Java.Interop-Tests exclusions #11099

Activity

1. dotnet-policy-service

   added

   needs-triageIssues that need to be assigned.Issues that need to be assigned.

   on Apr 9, 2026
2. simonrozsival

   added

   Area: CoreCLRIssues that only occur when using CoreCLR.Issues that only occur when using CoreCLR.

   copilot`copilot-cli` or other AIs were used to author this`copilot-cli` or other AIs were used to author this

   trimmable-type-map

   and removed

   needs-triageIssues that need to be assigned.Issues that need to be assigned.

   on Apr 9, 2026
3. simonrozsival

   added the

   Epic

   issue type on Apr 9, 2026
4. simonrozsival

   added this to the .NET 11 milestone on Apr 9, 2026
5. simonrozsival

   added a parent issue on Apr 9, 2026

   • [Epic] Trimmable Type Map for Native AOT and CoreCLR #10788
6. simonrozsival

   removed a parent issue on May 5, 2026

   • [Epic] Trimmable Type Map for Native AOT and CoreCLR #10788
7. simonrozsival

   added a parent issue on May 5, 2026

   • [TrimmableTypeMap] Run existing tests with trimmable type map #11017
8. simonrozsival

   added a commit that references this issue on May 21, 2026

   [TrimmableTypeMap] Add trimmable [Export] and [ExportField] callback …

   ...

   8f4c214
9. simonrozsival commented on May 25, 2026

   

   simonrozsival

   on May 25, 2026

   Last edited by simonrozsival

   MemberAuthor

   More actions

   Status update from origin/main (ec8c61e1b): several items in the original issue are already fixed or have moved to narrower follow-up tracking.

   Original checklist status

   • Remove TrimmableIgnore category — all 3 tests pass / are re-enabled

     • TrimmableIgnore no longer appears on origin/main.
     • JnienvTest.NewOpenGenericTypeThrows is enabled; the open-generic activation guard landed via [TrimmableTypeMap] Reject open generic JNI construction #11273 rather than the earlier closed [Mono.Android] Throw NotSupportedException for open generic type activation #11093.
     • JnienvTest.ActivatedDirectThrowableSubclassesShouldBeRegistered is enabled; UCO constructor activation fixes landed via [TrimmableTypeMap] Fix UCO constructor activations #11094 and later [TrimmableTypeMap] Fix UCO constructor activation #11275.
     • JavaObjectExtensionsTests.JavaCast_BaseToGenericWrapper is enabled; JavaCast/JavaAs + container support landed via [TrimmableTypeMap] JavaCast/JavaAs + container support #11225.

   • Remove SSL exclusion — all SSL tests are no longer excluded from the CoreCLRTrimmable lane

     • The CoreCLRTrimmable package-test lane now builds with -p:_AndroidTypeMapImplementation=trimmable -p:UseMonoRuntime=false and does not add SSL to ExcludeCategories.
     • SSL categories still exist on the tests themselves, and NativeAOT still excludes SSL, but that is separate from this trimmable typemap issue.

   • Remove or reduce ExcludedTestNames — Java.Interop-Tests fixtures run without SIGABRT

     • This has been reduced substantially. The original Java.Interop exact-name exclusions listed in this issue are no longer present except for Java.InteropTests.InvokeVirtualFromConstructorTests.
     • Current trimmable ExcludedTestNames on origin/main are:
       • Java.InteropTests.InvokeVirtualFromConstructorTests
       • Xamarin.Android.RuntimeTests.CustomWidgetTests.InflateCustomView_ShouldNotLeakGlobalRefs
     • The Java.Interop exclusion inventory/follow-up is now tracked by [TrimmableTypeMap] Trimmable typemap test exclusions inventory #11170.

   • Full parity: trimmable CoreCLR passes all tests that legacy CoreCLR passes

     • Not done yet while the remaining exact-name exclusions exist.

   Plan to fully close this issue

   1. Decide the disposition for Java.InteropTests.InvokeVirtualFromConstructorTests.

      • Current comments in NUnitInstrumentation.cs say this fixture depends on [JniAddNativeMethodRegistrationAttribute], which is unsupported by design under the trimmable typemap; [TrimmableTypeMap] Refuse [JniAddNativeMethodRegistrationAttribute] with XA4251 #11274 made this an explicit XA4251 error.
      • If that is the intended product behavior, this probably should remain as a documented unsupported scenario and be removed from this issue's closure criteria, with [TrimmableTypeMap] Trimmable typemap test exclusions inventory #11170 retaining the inventory context.
      • If we still want test parity here, the work is to provide a trimmable-compatible replacement path for that test scenario rather than making [JniAddNativeMethodRegistrationAttribute] work under trimmable.

   2. Investigate and fix Xamarin.Android.RuntimeTests.CustomWidgetTests.InflateCustomView_ShouldNotLeakGlobalRefs.

      • This is now the only remaining non-Java.Interop exact-name exclusion in the CoreCLRTrimmable runtime test instrumentation.
      • Reproduce with a Release CoreCLRTrimmable Mono.Android.NET-Tests run, compare against legacy CoreCLR, and inspect the custom view inflation/activation path for the leaked global ref.

   3. After those two exclusions are resolved or explicitly accepted as non-goals, remove the remaining ExcludedTestNames entries guarded by RuntimeFeature.TrimmableTypeMap.

   4. Run the full Mono.Android.NET-Tests CoreCLRTrimmable lane and compare against the normal CoreCLR lane. If there are no additional trimmable-only exclusions/failures, this issue can be closed.
10. simonrozsival commented on May 25, 2026

    

    simonrozsival

    on May 25, 2026

    MemberAuthor

    More actions

    Decision update:

    • Java.InteropTests.InvokeVirtualFromConstructorTests should remain permanently excluded for the trimmable typemap. This fixture depends on [JniAddNativeMethodRegistrationAttribute], which is unsupported by design under trimmable and now emits XA4251. We should treat this as a documented known limitation unless there is a customer request to implement a fully trimmable-compatible replacement path.

    • Xamarin.Android.RuntimeTests.CustomWidgetTests.InflateCustomView_ShouldNotLeakGlobalRefs is not related to the trimmable typemap and should not be an exact-name trimmable exclusion. I opened [tests] Remove custom widget trimmable exclusion #11483 to remove it from NUnitInstrumentation.cs. The test still has its normal test-level disposition, so any remaining global-ref-leak work should be handled independently of this trimmable typemap parity issue.
11. jonathanpeppers

    added a commit that references this issue on May 26, 2026

    [tests] Remove custom widget trimmable exclusion (#11483)

    ...

    8052934
12. jonathanpeppers

    closed this as completedin #11483on May 26, 2026
13. github-actions

    locked and limited conversation to collaborators on Jun 26, 2026