-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Drop GraalVM 19.2.1 support and deprecate enableJni option #6792
Drop GraalVM 19.2.1 support and deprecate enableJni option #6792
Conversation
166ab30
to
05516c4
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks very good. I added one question inline and I have another one: I wonder if adding the SunEC library is still necessary to get SSL working? But that's material for another PR if it ends up being useless.
(Marking as Request changes
so that we can discuss things before it being merged)
} else if (prop.getKey().equals("quarkus.jni.enable") && prop.getValue().equals("false")) { | ||
log.warn("Your application is setting the deprecated 'quarkus.jni.enable' configuration key to false." | ||
+ " Please consider removing this configuration key as it is ignored (JNI is always enabled) and it" | ||
+ " will be removed in a future Quarkus version."); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just to be sure: have you tested that you don't have several identical messages when setting quarkus.jni.enable=false
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I did it with #6306 but I'll restest it again with this PR just to be sure.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unless I missed something, this warning is never displayed with the current Quarkus codebase. I suppose this is an old property that is no longer used by the core extensions, but it can still be used by 3rd parties extensions.
On the other hand, the warning from JniProcessor
is displayed when quarkus.jni.enable
is set to false
.
I don't think we should worry about duplicate warnings here since it's very unlikely to happen.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Including the SunEC lib should not be required anymore, but I agree this should be treated separately.
I need to test this PR with JDK 11 in native mode (btw, thanks @geoand for your indications about how to do it with GitHub actions!), I'll promote the PR when I'm done with the tests.
Looking forward to it! Thanks @gwenneg! |
For the record, the GitHub action got triggered with these two changes in
and
|
It's really great to have this GH action available, I don't have to run JDK 11 native tests locally for an entire night anymore 😆 |
a78b6f6
to
493d1aa
Compare
I think 6 hours is the max. Did you try executing "only" the integration tests and nothing else like the current cron job does? |
The native tests got canceled after 3h 34m 19s at step 47/75 so it needs to run roughly for another couple hours (JDK 11 tests take so much time compared with the JDK 8 version...). I didn't change anything apart from the branch and job launch condition so it should behave like the current cron job. |
It seems the usual cron job runs these tests in approximately 5 hours so mine shouldn't be interrupted like that. Maybe there's an interruption cause unrelated with the tests duration. |
If you have one of the tests of the matrix failing, it auto-cancels the others AFAICS. |
Oh then the cancelation could be caused by the failure in the |
BTW, there's little change the report part can work in a PR as you're not supposed to have the token. And things shouldn't be reported to the same issues anyway. So I would drop that part. |
Like @gsmet mentioned, please change the reporting for your testing so we don't get mixed information in the issue :) |
8df9d6b
to
4fe96c9
Compare
The native integration tests run finally ended successfully for both GH actions. I'll check the absence of duplicate warnings about |
Excellent news! |
Looks like this Draft PR is ready to be promoted to a real PR? :) |
As long as the changes to the github actions are reverted :) |
@gastaldi It’s not ready to be promoted yet, I need to check for duplicate warnings locally first. And I will revert the actions changes of course. |
925005d
to
4c193ae
Compare
The JDK 11 native build and tests all passed successfully (see details here), the GitHub actions changes were removed and I'm done looking for duplicate warnings, so I'm promoting this PR. |
core/deployment/src/main/java/io/quarkus/deployment/pkg/NativeConfig.java
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. I'll let @gsmet review and decide when to land this PR
Merged, thanks. |
Fixes #6709 and #6101