Prevent use of GraalVM Native Build Tools Maven Plugin in parallel builds of project #32574
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:
org.apache.shardingsphere.infra.expr.espresso.EspressoInlineExpressionParserTest
from running on OpenJDK 22, mainly because the performance of Github Actions instrumentation was too low, and launching nested JVMs within JVMs often caused CI timeouts. The current PR restricts the relevant unit tests to run only under GraalVM CE. In fact, it can also run under local OpenJDK 21-24.apache/hive
4.0.0.Cloudera
that is driving the Apache Iceberg table format to replace the traditional Hive table format, not others.true
and prevent sharing the cache with other jobs. This helps to get rid of the tens of thousands of lines of CI Log to view the performance information of nativeTest. An example from https://github.com/apache/shardingsphere/actions/runs/10438004530?pr=32574 .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
.