[release/11.0-rc1] Disable ContextualReflection test on browser wasm - #132567
Merged
Conversation
Disable `Loader/ContextualReflection/ContextualReflection.csproj` for the CoreCLR browser target while the current browser WASM failure is being fixed. The condition matches existing Loader test exclusions and leaves the test enabled on other platforms and runtime flavors. Failure: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1556516&view=logs&jobId=33e61842-dc67-597b-7c8a-3f9fed635f50&j=33e61842-dc67-597b-7c8a-3f9fed635f50&t=5acdffa7-c2c6-5987-ba0a-609e87f6a40b Validation: - `CLRTestTargetUnsupported=true` for `RuntimeFlavor=coreclr`, `TargetOS=browser` - Property remains unset for `RuntimeFlavor=coreclr`, `TargetOS=windows` - `src\tests\build.cmd -Test Loader\ContextualReflection\ContextualReflection.csproj x64 checked` > [!NOTE] > This pull request description was generated with GitHub Copilot. Copilot-Session: fc7bc3bf-05c6-4992-9637-92b700491ec8
lewing
requested review from
davidwrighton and
jkotas
and
a lite review from Copilot
August 20, 2026 15:16
|
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. |
lewing
approved these changes
Aug 20, 2026
Contributor
|
Tagging subscribers to this area: @dotnet/runtime-infrastructure |
Contributor
There was a problem hiding this comment.
Pull request overview
This PR disables the Loader/ContextualReflection test project for the CoreCLR browser (WASM) target by setting CLRTestTargetUnsupported=true under an MSBuild condition, aligning with existing src/tests patterns for excluding unsupported CoreCLR browser tests.
Changes:
- Mark
ContextualReflection.csprojas unsupported whenRuntimeFlavor=coreclrandTargetOS=browser. - Add an
ActiveIssuecomment linking the tracking issue for the exclusion.
Member
|
/ba-g fast merge test disabling |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Backport of #132491 to release/11.0-rc1
/cc @lewing @davidwrighton
Customer Impact
[Select one or both of the boxes. Describe how this issue impacts customers, citing the expected and actual behaviors and scope of the issue. If customer-reported, provide the issue number.]
Regression
[If yes, specify when the regression was introduced. Provide the PR or commit if known.]
Testing
[How was the fix verified? How was the issue missed previously? What tests were added?]
Risk
[High/Medium/Low. Justify the indication by mentioning how risks were measured and addressed.]
IMPORTANT: If this backport is for a servicing release, please verify that:
release/X.0-staging, notrelease/X.0.release/X.0(no-stagingsuffix).Package authoring no longer needed in .NET 9
IMPORTANT: Starting with .NET 9, you no longer need to edit a NuGet package's csproj to enable building and bump the version.
Keep in mind that we still need package authoring in .NET 8 and older versions.