Skip to content
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

Fixes HotSpot JDK 22 CI failure due to GR-54293 #32267

Merged
merged 1 commit into from
Jul 25, 2024

Conversation

linghengqian
Copy link
Member

@linghengqian linghengqian commented Jul 25, 2024

Fixes https://github.com/apache/shardingsphere/actions/runs/10081728571/job/27887106603 .

Changes proposed in this pull request:

  • Fixes HotSpot JDK 22 CI failure due to GR-54293. Refer to [GR-54293] Allow multiple espresso runtime resources to coexist. oracle/graal#9020 . This is the change introduced by Uses GraalVM CE For JDK 22.0.2 in CI to prevent OutOfMemoryError #32246 .
  • Starting from GraalVM CE For JDK 22.0.2, using Truffle's Espresso implementation in OpenJDK requires including the RuntimeResourceId related Maven dependencies in the classpath, because Espresso's RuntimeResourceId is allowed to have multiple configurations. Currently, there is only one known implementation of RuntimeResourceId, which is org.graalvm.espresso:espresso-runtime-resources-linux-amd64:24.0.2. But I still think this is not reasonable, after all, I also need this Maven dependency on GraalVM CE For JDK 22.0.2.
  • The following figure uses SDKMAN! related sdk use java 21.0.2-open to verify that the execution of unit tests under HotSpot JDK has returned to normal.
  • image

Before committing this PR, I'm sure that I have checked the following options:

  • My code follows the code of conduct of this project.
  • I have self-reviewed the commit code.
  • I have (or in comment I request) added corresponding labels for the pull request.
  • I have passed maven check locally : ./mvnw clean install -B -T1C -Dmaven.javadoc.skip -Dmaven.jacoco.skip -e.
  • I have made corresponding changes to the documentation.
  • I have added corresponding unit tests for my changes.

@linghengqian linghengqian marked this pull request as ready for review July 25, 2024 11:06
Copy link
Member Author

@linghengqian linghengqian left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants