-
Notifications
You must be signed in to change notification settings - Fork 729
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
jdk_nio_0_FAILED java/nio/file/attribute/BasicFileAttributeView/CreationTime.java#tmp UnsatisfiedLinkError: Native Library libCreationTimeHelper.so already loaded in another classloader #19978
Comments
This kind of failure usually means that the test expected the class loader to be unloaded so that the subsequent loader could load the library. Class loader unloading is non-deterministic, so if this is the case, the test is simply invalid. |
This seems a new test behaviour introduced via ibmruntimes/openj9-openjdk-jdk21@2d5b7d5
RI passed however RI might have different class loader unloading implementations. Removing this from 0.48 milestone plan. |
I thought maybe we had implemented a workaround for this (GC if we fail to load a library for this reason), but maybe not. It's certainly something we could consider. |
@tajila fyi a deficiency exposed by a new test. |
This test doesn't intend to test It is not a VM issue. |
If it can be fixed as suggested in #19978 (comment) then it's VM. |
Okay, I see what GAC meant. |
@JasonFengJ9 For 0.48, this issue will need to be resolved by the end of this week. What's the current state of this issue? Based on this issue's impact, do we need it to be fixed in 0.48 or can it be pushed to 0.49? |
This is a long-existing issue, it isn't required for 0.48. Moving to 0.49. |
Issue Number: 19978 |
Failure link
From an internal build(
sles15s390x-svl-rt4-1
):Rerun in Grinder - Change TARGET to run only the failed test targets.
Optional info
Failure output (captured from console output)
50x internal grinder - 25/50 failed
Also seen at JDK21 x86-64_linux
JDK17 ppc64le_linux
The text was updated successfully, but these errors were encountered: