GraalVM native image build fails with JUnit 5.13.0 on GraalVM 21 and 24 #4624
Unanswered
michael-simons
asked this question in
Q&A
Replies: 3 comments 2 replies
-
I see, this seems to be bad timing |
Beta Was this translation helpful? Give feedback.
0 replies
-
So, I got the native image tools, build locally and tried with 0.11.0-SNAPSHOT and on Graal 21 I end up now with
with a useless Maven stack trace. GraalVM 24 is more helpful
|
Beta Was this translation helpful? Give feedback.
2 replies
-
@michael-simons The full list of build-time initialized classes I'm aware of is documented here: https://github.com/junit-team/junit5/wiki/Upgrading-to-JUnit-5.13 (linked from the release notes). Did you see that page? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I tried upgrading Neo4j-JDBC to JUnit 5.13, and suddenly native image tests fail:
https://github.com/neo4j/neo4j-jdbc/actions/runs/15384655216/job/43281320390#step:6:416
I See in the release notes that there are known changes:
We are already on 0.10.6
https://github.com/neo4j/neo4j-jdbc/blob/main/pom.xml#L184
https://github.com/neo4j/neo4j-jdbc/blob/b10c35bee6be2852063a4aa8d11b7b43057f85d8/neo4j-jdbc-it/neo4j-jdbc-it-cp/pom.xml#L119-L151
Graal 24 gives me at least enough indicators of classes that should be initialised at built time still:
I can add those, and it eventually still fails:
Now, this is a huge project, with Boot and Quarkus smoke tests as well, and those envs might use older JUnit versions, but I ofc checked that the failing project only uses 5.13:
In case anyone here has an idea, or wants to try it out, here's the smallest incarnation to do so:
@sormuras @alina-yur
Thank you!
Beta Was this translation helpful? Give feedback.
All reactions