GraalVM native image build fails with JUnit 5.13.0 on GraalVM 21 and 24 #4624

michael-simons · 2025-06-05T13:26:42Z

michael-simons
Jun 5, 2025

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:

The JUnit feature in GraalVM Native Build Tools has been rewritten to no longer require JUnit classes to be initialized at build time. Therefore, JUnit’s JARs no longer ship with native-image.properties files that contain --initialize-at-build-time options (introduced in 5.12.0). Please update to the most recent version of GraalVM Native Build Tools prior to upgrading to this version of JUnit

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:

Args = -H:ResourceConfigurationResources=${.}/resources-config.json \
  --initialize-at-build-time=org.junit.platform.launcher.core.HierarchicalOutputDirectoryProvider \
  --initialize-at-build-time=org.junit.platform.launcher.core.LauncherDiscoveryResult$EngineResultInfo \
  --initialize-at-build-time=org.junit.platform.launcher.core.DiscoveryIssueNotifier \
  --initialize-at-build-time=org.junit.jupiter.engine.descriptor.MethodBasedTestDescriptor$MethodInfo

I can add those, and it eventually still fails:

Error: Value not yet available for AnalysisField<ClassBasedTestDescriptor$ClassInfo.exclusiveResourceCollector -> HotSpotResolvedJavaFieldImpl<org.junit.jupiter.engine.descriptor.ClassBasedTestDescriptor$ClassInfo.exclusiveResourceCollector ExclusiveResourceCollector:32>, accessed: false, read: true, written: false, folded: false>

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:

./mvnw dependency:tree -pl neo4j-jdbc-it/neo4j-jdbc-it-cp

[INFO] Scanning for projects...
[INFO] 
[INFO] ---------------------< org.neo4j:neo4j-jdbc-it-cp >---------------------
[INFO] Building Neo4j JDBC Driver (IT on classpath) 6.5.1-SNAPSHOT
[INFO]   from pom.xml
[INFO] --------------------------------[ jar ]---------------------------------
[WARNING] The POM for org.neo4j:neo4j-jdbc:jar:6.5.1-SNAPSHOT is missing, no dependency information available
[WARNING] The POM for org.neo4j:neo4j-jdbc-translator-impl:jar:6.5.1-SNAPSHOT is missing, no dependency information available
[WARNING] The POM for org.neo4j:neo4j-jdbc-translator-sparkcleaner:jar:6.5.1-SNAPSHOT is missing, no dependency information available
[INFO] 
[INFO] --- dependency:3.6.0:tree (default-cli) @ neo4j-jdbc-it-cp ---
[INFO] org.neo4j:neo4j-jdbc-it-cp:jar:6.5.1-SNAPSHOT
[INFO] +- com.github.stefanbirkner:system-lambda:jar:1.2.1:test
[INFO] +- org.junit.platform:junit-platform-launcher:jar:1.13.0:test
[INFO] |  +- org.junit.platform:junit-platform-engine:jar:1.13.0:test
[INFO] |  |  +- org.opentest4j:opentest4j:jar:1.3.0:test
[INFO] |  |  \- org.junit.platform:junit-platform-commons:jar:1.13.0:test
[INFO] |  \- org.apiguardian:apiguardian-api:jar:1.1.2:test
[INFO] +- org.mockito:mockito-core:jar:5.18.0:test
[INFO] |  +- net.bytebuddy:byte-buddy:jar:1.17.5:test
[INFO] |  +- net.bytebuddy:byte-buddy-agent:jar:1.17.5:test
[INFO] |  \- org.objenesis:objenesis:jar:3.3:test
[INFO] +- org.neo4j:neo4j-jdbc:jar:6.5.1-SNAPSHOT:test
[INFO] +- org.neo4j:neo4j-jdbc-translator-impl:jar:6.5.1-SNAPSHOT:test
[INFO] +- org.neo4j:neo4j-jdbc-translator-sparkcleaner:jar:6.5.1-SNAPSHOT:test
[INFO] +- org.slf4j:slf4j-simple:jar:2.0.17:test
[INFO] |  \- org.slf4j:slf4j-api:jar:2.0.17:test
[INFO] +- org.testcontainers:junit-jupiter:jar:1.21.0:test
[INFO] |  \- org.testcontainers:testcontainers:jar:1.21.0:test
[INFO] |     +- junit:junit:jar:4.13.2:test
[INFO] |     |  \- org.hamcrest:hamcrest-core:jar:1.3:test
[INFO] |     +- org.apache.commons:commons-compress:jar:1.24.0:test
[INFO] |     +- org.rnorth.duct-tape:duct-tape:jar:1.0.8:test
[INFO] |     |  \- org.jetbrains:annotations:jar:17.0.0:test
[INFO] |     +- com.github.docker-java:docker-java-api:jar:3.4.2:test
[INFO] |     |  \- com.fasterxml.jackson.core:jackson-annotations:jar:2.19.0:test
[INFO] |     \- com.github.docker-java:docker-java-transport-zerodep:jar:3.4.2:test
[INFO] |        +- com.github.docker-java:docker-java-transport:jar:3.4.2:test
[INFO] |        \- net.java.dev.jna:jna:jar:5.13.0:test
[INFO] +- org.testcontainers:neo4j:jar:1.21.0:test
[INFO] +- org.assertj:assertj-core:jar:3.27.3:test
[INFO] \- org.junit.jupiter:junit-jupiter:jar:5.13.0:test
[INFO]    +- org.junit.jupiter:junit-jupiter-api:jar:5.13.0:test
[INFO]    +- org.junit.jupiter:junit-jupiter-params:jar:5.13.0:test
[INFO]    \- org.junit.jupiter:junit-jupiter-engine:jar:5.13.0:test
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  1.265 s
[INFO] Finished at: 2025-06-05T15:23:31+02:00
[INFO] ------------------------------------------------------------------------

In case anyone here has an idea, or wants to try it out, here's the smallest incarnation to do so:

./mvnw -U -DskipClusterIT -Dnative clean verify  -pl neo4j-jdbc-it/neo4j-jdbc-it-cp -am

@sormuras @alina-yur

Thank you!

michael-simons · 2025-06-05T13:31:23Z

michael-simons
Jun 5, 2025
Author

I see, this seems to be bad timing

graalvm/native-build-tools#693

@marcphilipp

0 replies

michael-simons · 2025-06-05T13:55:20Z

michael-simons
Jun 5, 2025
Author

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

Error: Feature defined by org.graalvm.junit.platform.JUnitPlatformFeature unexpectedly failed with a(n) java.lang.RuntimeException. Please report this problem to the authors of org.graalvm.junit.platform.JUnitPlatformFeature.

with a useless Maven stack trace.

GraalVM 24 is more helpful

Error: Feature defined by org.graalvm.junit.platform.JUnitPlatformFeature unexpectedly failed with a(n) java.lang.RuntimeException. Please report this problem to the authors of org.graalvm.junit.platform.JUnitPlatformFeature.
Caused by: java.lang.RuntimeException: Cannot compute test selectors from test ids.
	at org.graalvm.junit.platform.JUnitPlatformFeature.getSelectors(JUnitPlatformFeature.java:147)
	at org.graalvm.junit.platform.JUnitPlatformFeature.beforeAnalysis(JUnitPlatformFeature.java:112)
	at org.graalvm.nativeimage.builder/com.oracle.svm.hosted.NativeImageGenerator.lambda$runPointsToAnalysis$0(NativeImageGenerator.java:808)
	at org.graalvm.nativeimage.builder/com.oracle.svm.hosted.FeatureHandler.forEachFeature(FeatureHandler.java:93)
	at org.graalvm.nativeimage.builder/com.oracle.svm.hosted.NativeImageGenerator.runPointsToAnalysis(NativeImageGenerator.java:808)
	at org.graalvm.nativeimage.builder/com.oracle.svm.hosted.NativeImageGenerator.doRun(NativeImageGenerator.java:567)
	at org.graalvm.nativeimage.builder/com.oracle.svm.hosted.NativeImageGenerator.run(NativeImageGenerator.java:533)
	at org.graalvm.nativeimage.builder/com.oracle.svm.hosted.NativeImageGeneratorRunner.buildImage(NativeImageGeneratorRunner.java:545)
	at org.graalvm.nativeimage.builder/com.oracle.svm.hosted.NativeImageGeneratorRunner.build(NativeImageGeneratorRunner.java:732)
	at org.graalvm.nativeimage.builder/com.oracle.svm.hosted.NativeImageGeneratorRunner.start(NativeImageGeneratorRunner.java:151)
	at org.graalvm.nativeimage.builder/com.oracle.svm.hosted.NativeImageGeneratorRunner.main(NativeImageGeneratorRunner.java:99)

2 replies

marcphilipp Jun 5, 2025
Maintainer

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
Error: Feature defined by org.graalvm.junit.platform.JUnitPlatformFeature unexpectedly failed with a(n) java.lang.RuntimeException. Please report this problem to the authors of org.graalvm.junit.platform.JUnitPlatformFeature.
with a useless Maven stack trace.

Sounds like a problem (bug?) in Native Build Tools. Could you please raise an issue there and link it here?

michael-simons Jun 5, 2025
Author

Done: graalvm/native-build-tools#738

marcphilipp · 2025-06-05T14:54:12Z

marcphilipp
Jun 5, 2025
Maintainer

@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?

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

GraalVM native image build fails with JUnit 5.13.0 on GraalVM 21 and 24 #4624

Uh oh!

{{title}}

Uh oh!

Replies: 3 comments 2 replies

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Select a reply

Uh oh!

Uh oh!

GraalVM native image build fails with JUnit 5.13.0 on GraalVM 21 and 24 #4624

Uh oh!

michael-simons Jun 5, 2025

Replies: 3 comments · 2 replies

Uh oh!

michael-simons Jun 5, 2025 Author

Uh oh!

michael-simons Jun 5, 2025 Author

Uh oh!

marcphilipp Jun 5, 2025 Maintainer

Uh oh!

michael-simons Jun 5, 2025 Author

Uh oh!

marcphilipp Jun 5, 2025 Maintainer

michael-simons
Jun 5, 2025

Replies: 3 comments 2 replies

michael-simons
Jun 5, 2025
Author

michael-simons
Jun 5, 2025
Author

marcphilipp Jun 5, 2025
Maintainer

michael-simons Jun 5, 2025
Author

marcphilipp
Jun 5, 2025
Maintainer