-
Notifications
You must be signed in to change notification settings - Fork 737
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VmArgumentTests_0_FAILED FAILED: testMemoryLeaks #20810
Comments
Issue Number: 20810 |
Issue eclipse-openj9#20810 Signed-off-by: Peter Shipton <[email protected]>
Exclude the test via #20982 |
@JasonFengJ9 The failure reported in this issue was also reported in the below issues. Can we consolidate these failures into a single issue? This failure is also seen with other JDKs; do we need to target it against the JDK24 milestone? |
I closed those obsolete issues from 2018/19. I assume what Jason reported is a new failure, which I'm not seeing on any other version in the open source builds (not even intermittently). I don't know if it's intermittent on jdk24 or not. |
I did see the same failure in https://openj9-jenkins.osuosl.org/job/Test_openjdk24_j9_extended.functional_aarch64_mac_Nightly/1, which is why I temporarily excluded it, until this can be fixed. |
@babsingh I haven't seen it in recent nightly/weekly runs other than JDK24. Those two obsolete issues probably were already fixed. |
@JasonFengJ9, could you assist with triaging this failure? |
Update: The testMemoryLeaks() run with openj9/jcl/src/java.base/share/classes/java/lang/J9VMInternals.java Lines 158 to 160 in 64284dd
Thread "Common-Cleaner" is still alive after running the shutdown hooks. is seen with -verbose:shutdown .
The thread ignored t.interrupt() at https://github.com/ibmruntimes/openj9-openjdk-jdk24/blob/098ff2661e34fe1ab01655a491402543ea6a14e5/src/java.base/share/classes/jdk/internal/ref/CleanerImpl.java#L145-L146 |
From an internal build:
Rerun in Grinder - Change TARGET to run only the failed test targets.
Optional info
Failure output (captured from console output)
The text was updated successfully, but these errors were encountered: