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

Pass -H:+UnlockExperimentalVMOptions as necessary with Graalvm 23.1 #35379

Merged
merged 1 commit into from
Aug 20, 2023

Conversation

zakkak
Copy link
Contributor

@zakkak zakkak commented Aug 16, 2023

Needed since oracle/graal#7190 to avoid warnings

Edit:

The implementation is surrounding the experimental option with enabling/disabling unlock to limit the scope as suggested in oracle/graal#7105 (comment). Alternatively we could just pass -H:+UnlockExperimentalVMOptions as the first option and allow any experimental option to be passed afterwards. It would make things simpler but would also allow people (both Quarkus users and devs) to use experimental options possibly without noticing.

@gsmet
Copy link
Member

gsmet commented Aug 16, 2023

@zakkak which versions of Quarkus are using 23.1? Should it be backported?

@zakkak
Copy link
Contributor Author

zakkak commented Aug 16, 2023

@zakkak which versions of Quarkus are using 23.1?

None yet, 23.1 (or GraalVM for JDK 21) is still in development and planned to be released mid-September

Should it be backported?

No

@gsmet
Copy link
Member

gsmet commented Aug 16, 2023

Cancelling CI for now as it is saturated. I will restart this later.

@gsmet gsmet force-pushed the 2023-08-16-23.1-updates branch from 0e6ef31 to 1a1d4ea Compare August 17, 2023 16:18
Comment on lines +1017 to +1024
private void addExperimentalVMOption(List<String> nativeImageArgs, String option) {
if (graalVMVersion.compareTo(GraalVM.Version.VERSION_23_1_0) >= 0) {
nativeImageArgs.add("-H:+UnlockExperimentalVMOptions");
}
nativeImageArgs.add(option);
if (graalVMVersion.compareTo(GraalVM.Version.VERSION_23_1_0) >= 0) {
nativeImageArgs.add("-H:-UnlockExperimentalVMOptions");
}
Copy link
Member

Choose a reason for hiding this comment

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

So you're surrounding the experimental option with enabling/disabling unlock? Is it really how it works? Never seen something similar :).

Copy link
Contributor Author

@zakkak zakkak Aug 17, 2023

Choose a reason for hiding this comment

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

Correct, this is to limit the scope as suggested in oracle/graal#7105 (comment). Alternatively we could just pass -H:+UnlockExperimentalVMOptions as the first option and allow any experimental option to be passed afterwards. It would make things simpler but would also allow people (both Quarkus users and devs) to use experimental options possibly without noticing.

@quarkus-bot
Copy link

quarkus-bot bot commented Aug 17, 2023

Failing Jobs - Building 1a1d4ea

Status Name Step Failures Logs Raw logs
JVM Tests - JDK 11 Build Failures Logs Raw logs
✔️ JVM Tests - JDK 17
✔️ JVM Tests - JDK 20

Full information is available in the Build summary check run.

Failures

⚙️ JVM Tests - JDK 11 #

- Failing: core/deployment 
! Skipped: devtools/cli devtools/gradle/gradle-application-plugin devtools/gradle/gradle-extension-plugin and 569 more

📦 core/deployment

io.quarkus.deployment.dev.FileSystemWatcherTestCase.testFileSystemWatcher line 106 - More details - Source on GitHub

org.opentest4j.AssertionFailedError: expected: not <null>
	at org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:152)
	at org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132)

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