Narrow browser WASM R2R test exclusions

[lewing]

Summary

Narrowly suppress the confirmed WASM ReadyToRun failure shapes tracked by #131886, #133259, #133303, and #133307 so the browser R2R lane can be restored without losing interpreter or unaffected-platform coverage.

• use method-level ActiveIssue conditions for Runtime_79354 and Runtime_58874, scoped to WASM R2R
• treat an empty Assembly.Location as an unsupported premise in Runtime_117566, following review feedback from [WIP] Fix test failure for Regression_o_2 browser-wasm R2R incompatibilities #133274
• mark the merged Interop work item R2R-incompatible on CoreCLR Wasm because Crossgen2 aborts before execution while resolving TypeMapApp metadata
• skip only the failing generic multidimensional-array subtest in the manual Crossgen2 smoke runner, using PlatformDetection.IsWasm and PlatformDetection.IsReadyToRunCompiled

This intentionally does not suppress #133219, #133221, #133224, #133286, or the remaining unclassified failure shapes in #133305. Exact-base R2R evidence shows b125091 now passes, and the current-main R2R baseline also shows pinnedlocal passing when reached.

Testing

• built all affected standalone and merged runtime-test projects
• ran the affected local non-R2R wrapper scripts
• inspected generated merged-runner conditions for the method-level exclusions
• exact-base browser R2R baseline Enable browser WASM R2R tests in manual pipeline #133308 reproduced every retained target failure while b125091 passed
• ordinary browser-WASM CI executed and passed all affected tests, including all 70 ReadyToRun smoke subtests
• purpose-built WASI comparison reproduced the Runtime_79354, Runtime_117566, Runtime_58874, and generic multidimensional-array R2R failures while their interpreter controls passed
• applying the exact Runtime_117566 empty-location guard on WASI made both interpreter and R2R executions pass
• purpose-built WASI comparison confirmed the full Interop composite aborts before execution while TypeMapApp individually compiles and passes
• regenerated WASI Interop with the parent R2RIncompatible property: interpreter ran 57/57 and R2R skipped before compilation with exit 0
• confirmed the merged Interop exclusion is set for browser-wasm and wasi-wasm but unset for native targets

The broader WASI work items remain outside the curated lane: Regression_o_3 has three additional Assembly.Location failures, and Regression_1 later aborts in csharptester, even though b125091 itself passes.

Note

This pull request was created with GitHub Copilot assistance.

[azure-pipelines]

Azure Pipelines:
Successfully started running 3 pipeline(s).
13 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.

[dotnet-policy-service]

Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch
See info in area-owners.md if you want to be subscribed.

[Copilot]

🟡 Changes recommended

One change makes a test silently pass via early-return when Assembly.Location is empty; it should be an explicit skip (or fail-fast outside the intended platform) to avoid masking regressions.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Pull request overview

This pull request narrows browser-WASM ReadyToRun (R2R) test suppressions to specific known-failing scenarios so the R2R lane can be re-enabled while preserving coverage elsewhere.

Changes:

• Skip the TestGenericMDArrayBehavior crossgen2 smoke subtest only for browser + R2R execution.
• Apply method-level ActiveIssue conditions for specific xUnit regression tests that fail only under browser + R2R.
• Mark TypeMapApp as R2R-incompatible only for CoreCLR browser builds to avoid crossgen2 compile-time failure.

File summaries

File	Description
src/tests/readytorun/crossgen2/Program.cs	Conditionally avoids running the generic MD-array behavior test under browser R2R.
src/tests/JIT/Regression/JitBlue/Runtime_79354/Runtime_79354.cs	Adds ActiveIssue gating for browser R2R.
src/tests/JIT/Regression/JitBlue/Runtime_58874/Runtime_58874.cs	Adds ActiveIssue gating for browser R2R.
src/tests/JIT/Regression/JitBlue/Runtime_117566/Runtime_117566.cs	Avoids LoadFromAssemblyPath when Assembly.Location is empty.
src/tests/JIT/Regression/CLR-x86-JIT/V2.0-Beta2/b125091/b125091.il	Adds ActiveIssue gating for browser R2R in the IL test.
src/tests/Interop/TypeMap/TypeMapApp.csproj	Marks the TypeMap test app as R2R-incompatible only for CoreCLR browser builds.

Review details

• Files reviewed: 6/6 changed files
• Comments generated: 1
• Review effort level: Lite

[lewing]

I opened #133308 to allow testing against partial disabling while we work through the issues

[dotnet-policy-service]

Tagging subscribers to 'arch-wasm': @lewing, @pavelsavara
See info in area-owners.md if you want to be subscribed.

[Copilot]

🟡 Changes recommended

The new browser+R2R guard skips the entire TestGenericMDArrayBehavior test (multiple sub-checks), which is broader than the intended “single failing subtest” suppression and unnecessarily drops coverage.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Review details

• Files reviewed: 6/6 changed files
• Comments generated: 1
• Review effort level: Lite

[Copilot]

🟡 Changes recommended

Interop.csproj’s new R2RIncompatible condition currently applies to all CoreCLR WASM targets (not browser-only), which conflicts with the stated intent and risks dropping WASI R2R coverage unintentionally.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Review details

• Files reviewed: 6/6 changed files
• Comments generated: 1
• Review effort level: Lite

[lewing]

/azp run runtime-wasm-non-libtests

[azure-pipelines]

Azure Pipelines:
Successfully started running 1 pipeline(s).

[Copilot]

🟢 Approval recommended

The changes are narrowly scoped to test gating/infrastructure for known WASM R2R failures, with only a minor maintainability improvement suggested around making the smoke-test skip explicit in output.

Review details

• Files reviewed: 6/6 changed files
• Comments generated: 1
• Review effort level: Lite