-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Deleted jdk.internal.loader.NativeLibrary::findEntry0
reachable in JDK 22+25 builds
#7894
Comments
/cc @zapster |
@jerboaa @zakkak I'm not able to follow your instructions:
In addition, which revison of quarkus did you use (I tried |
Sorry for that.
I can reproduce with latest
Please use OpenJDK 17.0.9+9 as |
Thanks @zakkak. Another problem with
was running into concurrency issues with the maven dependency downloads. Removing the The next problem was with
It seems that the GraalVM version check does not like dev builds.
Is there some workaround for this? If not, can the version check be improved? Long story short, I was not able to reproduce the problem with the provided instructions. However, I was able to reproduce the problem locally via some internal benchmarking command and will look for a solution. |
Unfortunately I am not aware of any way to build only the necessary modules required for a specific integration test. I would have to create an external reproducer which I found not trivial since this only popped up in the AWT integration test which is quite complex.
In the github actions we work around this by not building a native image for graal/.github/workflows/quarkus.yml Lines 116 to 120 in ddb574c
Good to hear. Sorry for the trouble with the reproducer. |
Thanks @zakkak for the heads up! |
After merging in the latest version, the problem disappeared. Closing. |
Describe the issue
After the upgrade to JDK 22+25 the deleted
jdk.internal.loader.NativeLibrary::findEntry0
appears to be reachable.Steps to reproduce the issue
Describe GraalVM and your environment:
More details
Full log:
The text was updated successfully, but these errors were encountered: