Disable failing weak reference leak test - #11755
Merged
jonathanpeppers merged 1 commit intoJun 26, 2026
Merged
Conversation
Refs #11690 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Disables a flaky/failing GC bridge test related to weak reference leak detection while a NativeAOT-specific regression is investigated (tracked in #11690).
Changes:
- Adds an NUnit attribute to skip
Java.InteropTests.JnienvTest.DoNotLeakWeakReferencesand links the ignore reason to the tracking issue.
Show a summary per file
| File | Description |
|---|---|
| tests/Mono.Android-Tests/Mono.Android-Tests/Java.Interop/JnienvTest.cs | Marks DoNotLeakWeakReferences as ignored due to a NativeAOT failure, referencing the tracking issue. |
Copilot's findings
- Files reviewed: 1/1 changed files
- Comments generated: 1
jonathanpeppers
approved these changes
Jun 26, 2026
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The
Java.InteropTests.JnienvTest.DoNotLeakWeakReferencestest is very flaky and we should look into why that is - is there a bug in the gc bridge/value manager/somewhere else or is it just the test that's unreliable?There is an existing issue to look into this problem: #11690
Testing
git diff --check -- tests/Mono.Android-Tests/Mono.Android-Tests/Java.Interop/JnienvTest.cs