Skip to content

Simplify SubscribeToAppDomainUnhandledException test to be CoreCLR-specific#11716

Draft
Copilot wants to merge 16 commits into
mainfrom
copilot/wip-simplify-dotnet-11-mobile-runtime-test
Draft

Simplify SubscribeToAppDomainUnhandledException test to be CoreCLR-specific#11716
Copilot wants to merge 16 commits into
mainfrom
copilot/wip-simplify-dotnet-11-mobile-runtime-test

Conversation

Copilot AI commented Jun 23, 2026

Copy link
Copy Markdown
Contributor

Thanks for the feedback on #11632. This PR addresses the review comment by simplifying the SubscribeToAppDomainUnhandledException test.

Original PR: #11632
Triggering review: #11632 (comment)

@copilot simplify this test in a separate PR: it should be CoreCLR specific, no need for the AndroidRuntime runtime parameter and the test body can be simplified quite a bit too.

Changes

  • Removed the [Values(AndroidRuntime.CoreCLR, AndroidRuntime.NativeAOT)] AndroidRuntime runtime parameter — the test is now CoreCLR-specific with no parameterization
  • Removed the IgnoreUnsupportedConfiguration guard — unnecessary for a single, always-supported configuration
  • Removed the NativeAOT-specific Assert.Ignore block
  • Removed PackageUtils.MakePackageName(runtime) — only needed when testing multiple runtimes to avoid package name collisions
  • Replaced the expectedSender switch expression with a hardcoded expected string (null formats as empty in Console.WriteLine)

kotlarmilos and others added 15 commits June 15, 2026 18:13
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
The MAUI integration stage installs the full maui workload, which pulls
mobile runtime workloads that are no longer produced for .NET 11. Remove
the stage from the public and internal pipelines and drop the now-unused
RunMAUITestJob variable.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…able

Address review feedback: the native build and MAUI-on-local-build flow still
require the Mono runtime pack downloads and workload-install targets, so restore
package-download.proj, DotNet.targets, Step_InstallDotNetPreview, the xaprepare
property plumbing, the maui_tests stage, and the RunMAUITestJob variable. The PR
now changes only the Mono mobile instrumentation test legs in
stage-package-tests.yaml plus the temporary validation pins.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Surface the unsupported Mono mobile runtime build error directly in the
workload to validate that no Mono mobile build paths remain in CI.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Validation now happens through the temporary Mono mobile runtime build
error in the workload, so the pinned SDK version and validation package
feed are no longer needed.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Gate the MonoVM runtime parametrization in the build tests so the Mono
variants are ignored on .NET 11 and later, where the Mono runtime is no
longer supported for Android. CoreCLR and NativeAOT variants are
unaffected.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
The Mono runtime is no longer supported for Android in .NET 11 and later.
Remove the Mono runtime variants from the build tests:

- Narrow the runtime parametrization ([Values], [TestCase], and the
  Enum.GetValues/TestCaseSource generators) to CoreCLR and NativeAOT.
- Delete the Mono-only test methods and their now-unused TestCaseSource
  data generators.

CoreCLR and NativeAOT coverage is unchanged.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
The Mono mobile runtime is no longer supported for Android in .NET 11, so
building a project with UseMonoRuntime=true now errors with NETSDK1242. The
device integration test suite still enumerated AndroidRuntime.MonoVM through
[Values], Enum.GetValues, [Values(...)] and [TestCase(...)], causing those
emulator legs to fail. Drop the MonoVM variants and keep CoreCLR and NativeAOT,
matching the conversion already applied to Xamarin.Android.Build.Tests.

Mono-only tests (AOT profiler, interpreter, LLVM, AppDomain.UnhandledException,
and the MonoVM-only debugger break tests) are removed. Tests that merely pinned
MonoVM now use the default CoreCLR runtime.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
LoggingPropsShouldCreateOverrideDirForRelease set debug.mono.log and asserted
methods.txt in the .__override__ directory, behavior that only the Mono runtime
produces. With the MonoVM pin dropped the test ran on CoreCLR, where methods.txt
is never emitted, so it failed. Remove the test; CoreCLR has no equivalent output.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Remove the temporary _ErrorOnMonoMobileRuntime target now that CI
confirms no test legs build the Mono mobile runtime. The unsupported
configuration is enforced by the SDK.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Restore SubscribeToAppDomainUnhandledException for CoreCLR/NativeAOT
instead of deleting it. Remove the now-unused SettingCombinationsSource
in InvalidConfigTests. Restore VersionCodeTests to preserve
AndroidCreatePackagePerAbi coverage, ignored with a TODO until the test
data is reworked for CoreCLR/NativeAOT supported ABIs.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
The test body already routes CoreCLR to a null unhandled-exception sender,
so only NativeAOT needs to stay skipped. Aligns with #11673.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: simonrozsival <374616+simonrozsival@users.noreply.github.com>
Copilot AI changed the title [WIP] [WIP] Simplify .NET 11 mobile runtime test as per review feedback Simplify SubscribeToAppDomainUnhandledException test to be CoreCLR-specific Jun 23, 2026
Copilot AI requested a review from simonrozsival June 23, 2026 11:30
Base automatically changed from dev/update-sdk-mobile to main June 23, 2026 13:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants