-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Update to GraalVM / Mandrel 22.3.0 #28861
Conversation
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.
Needs rebasing now that #28843 got merged.
Let me rebase it. |
Done! We still need to adjust the Mandrel image version when available but I updated the doc version as it won't break anything. |
@@ -16,7 +16,7 @@ | |||
@ConfigRoot(phase = ConfigPhase.BUILD_TIME) | |||
public class NativeConfig { | |||
|
|||
public static final String DEFAULT_GRAALVM_BUILDER_IMAGE = "quay.io/quarkus/ubi-quarkus-graalvmce-builder-image:22.2-java17"; | |||
public static final String DEFAULT_GRAALVM_BUILDER_IMAGE = "quay.io/quarkus/ubi-quarkus-graalvmce-builder-image:22.3-java17"; | |||
public static final String DEFAULT_MANDREL_BUILDER_IMAGE = "quay.io/quarkus/ubi-quarkus-mandrel-builder-image:22.2-java17"; |
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.
To make sure we won't forget: we need to update that one when ready.
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.
quay.io/quarkus/ubi-quarkus-mandrel-builder-image:22.3-java17
is there now, fwiw.
@zakkak I see the build failing with:
Did we miss something when ensuring |
Hmmm, indeed. Unfortunately Quarkus uses the defined Regarding this specific failure, it's because So it looks like we will need to patch the source code accordingly and bump the minimum version to 22.3 or remove the non public API annotations. |
I pushed an update to move to the new package. Rationale explained in the commit comment. |
@zakkak unfortunately, it cannot be backported, at least not directly. |
Oh, I see. Shall we keep the label though to indicate that we need this in 2.13 as well? |
Yes, let's keep the label so that we don't miss it. |
@cescoffier what's the status of this build in your fork? Did you see other problems? |
Nope, looks good. |
FYI, due to some infrastructure related issues this might take a bit longer than usual. |
Mandrel 22.3 is now released. I have also openned quarkusio/quarkus-images#215 to generate the quarkus images. @cescoffier are you going to update this PR to include the Mandrel images as well? |
9a9b64e
to
6c5700f
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.
LGTM, thanks @cescoffier
This annotation has moved to a new package and we need to use the 22.3 version to make sure our code compiles. As for using 22.2, it still works but the annotation is ignored, which looks OK as the annotation is not used in places where it is strictly necessary. If people use the recommended GraalVM version, everything will be fine. If not, things will mostly work anyway.
I rebased to trigger CI as it was in limbo. |
I see errors in our daily native runs, it's apparently because of oracle/graal#5303 bug Shouldn't we set mandrel image as default for now? Peter has commented on the issue that Mandrel 22.3 works for him. |
@gsmet I am marking this as a "noteworthy" feature for better visibility. (inspired by discussion in https://quarkusio.zulipchat.com/#narrow/stream/187030-users/topic/Quarkus.20won't.20build.20native/near/307716675) |
@galderz / @zakkak do you think oracle/graal#5303 is gonna be fixed soon? |
@rsvoboda I really don't know. I personally have not seen this issue happen in any of the machines I have access to. I would suggest commenting on the upstream issue and possibly providing more info about the context under which the issue is triggered. Regarding switching to Mandrel by default I am +0. People getting hit by the issue can easily switch to Mandrel by passing |
ok, I will comment upstream |
DO NOT MERGE!