-
Notifications
You must be signed in to change notification settings - Fork 720
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
java.lang.IllegalAccessException thrown for jdk.internal.misc.Unsafe.theUnsafe in Valhalla vt_standard testing #20372
Comments
@theresa-m, @a7ehuo - FYI |
Issue Number: 20372 |
The failed line is:
@JasonFengJ9 Do you know if this fails on regular JDK24 build ? |
Currently, there are no JDK24 nightly builds. |
Those failed tests in openjdknext_j9_sanity.functional_x86-64_linux_vt_standard passed in a regular openjdkNext_j9_sanity.functional_x86-64_linux
FYI @hangshao0 |
Have you seen this failure before ? @babsingh @fengxue-IS The https://github.com/ibmruntimes/openj9-openjdk-jdk.valuetypes repo is a few weeks behind https://github.com/ibmruntimes/openj9-openjdk-jdk though. |
Two possible solutions come to mind:
|
It seems new. I haven't seen it before. |
I tried the failing code with old Valhalla nightly builds and it started failing after the https://github.com/ibmruntimes/openj9-openjdk-jdk.valuetypes update in early May. |
I looked through the merge commits of these files from the May extensions update but did not see anything inconsistent with the https://github.com/ibmruntimes/openj9-openjdk-jdk repository. This list is a subset of files identified as having had conflicts in ibmruntimes/openj9-openjdk-jdk.valuetypes#10, ibmruntimes/openj9-openjdk-jdk.valuetypes#11, ibmruntimes/openj9-openjdk-jdk.valuetypes#12
|
I'm inclined to believe that openjdk hasn't finished updating the |
Many test failures are seen in recent PR sanity.functional testing with {x|z|a|p}linuxvalst (i.e., vt_standard) for pull requests #20112 and #20332. In most, if not all, cases
IllegalAccessExceptions
are thrown. I was able to reproduce this in an internal personal build with the latest merged source.The text was updated successfully, but these errors were encountered: