Bump Junit Platform to 5.10.3 to support using @EnabledInNativeImage
on the test classes
#31982
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For #29052.
Changes proposed in this pull request:
@EnabledInNativeImage
failure in some unit tests #30031 . Bump Junit Platform to 5.10.3 to support using@EnabledInNativeImage
on the test classes. Refer to@EnabledInNativeImage
is not properly supported at the class level junit-team/junit5#3745 .org.graalvm.polyglot:polyglot
to 24.0.1. This is mainly to further reduce the total execution time of the unit tests oforg.apache.shardingsphere:shardingsphere-infra-expr-espresso
.com.github.docker-java:docker-java-api:3.3.6
began to require additional GraalVM Reachability Metadata. Refer to com.github.dockerjava.api.model.RuntimeInfo oracle/graalvm-reachability-metadata#492 .39567
in Seata's unit tests.Before committing this PR, I'm sure that I have checked the following options:
./mvnw clean install -B -T1C -Dmaven.javadoc.skip -Dmaven.jacoco.skip -e
.