-
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
Ecosystem CI for Google Cloud Services fails with Quarkus main #25501
Comments
I tried this with Quarkus 2.9.0.Final and 22.0 and it works as expected, while with 22.1 it fails. So as a first step @gsmet we might want to reconsider the backport of #25366 to 2.9.1. The issue is already reported upstream as well oracle/graal#4543 |
I think I understand what's going on. Google native image support have this dependency:
It's provided but as we switch to the new artifact I'll open an issue on there side for us to migrate to the new artifact. |
They are aware of the issue at Google side and someone already report it for Camel Quarkus, see GoogleCloudPlatform/native-image-support-java#393 |
@loicmathieu there is no switch from This, however, shouldn't cause any issues (see #25366 (comment)). I am still investigating it but I believe that this is a GraalVM bug. |
@zakkak thanks, I mis-understood it. This will be a blocker for Quarkus 2.10 platform release. |
Can we work around it? Because I doubt we will have a fix in GraalVM by then and AFAICS it should just be about making a class runtime initialized? |
@gsmet I'll try to dig a little deeper tomorrow on this one but it seems to be an issue on GraalVM 22.1, Google team is working on it and the stacktrace lead to nothing inside our (or Google's) code base so it may be hard to solve on our side. I don't know if @zakkak had some time to have a look as I don't know how to work on this, it didn't seems to be "just about making a class runtime initialized" or maybe but I have no idea which one. |
Work around quarkusio#25501 until oracle/graal#4543 gets resolved
We can work around it this way for now, but it's certainly not a proper fix. Done in #25598 |
Work around quarkusio#25501 until oracle/graal#4543 gets resolved
Work around quarkusio#25501 until oracle/graal#4543 gets resolved
Update: A proper fix has landed in GoogleCloudPlatform/native-image-support-java#395 and is expected to be released this week. |
The fix has been released, we will know tomorrow if it works as I cannot relaunch the ecosystem CI. |
@loicmathieu can you please confirm whether this is now fixed? |
Yes it was ok 2 months ago I forgot to close the issue. Closing it now. |
Describe the bug
The Quarkiverse extension Google Cloud Services fails to runs the ecosystem CI due to an issue to build a native image with the current Quarkus main.
See the failing build: https://github.com/quarkiverse/quarkus-google-cloud-services/actions/runs/2304956797
Expected behavior
Eciosystem CI build is OK
Actual behavior
It fails with
How to Reproduce?
This can be reproduced using the integration test of the extension pack.
Fork the repository: https://github.com/quarkiverse/quarkus-google-cloud-services
Update the pom.xml to use Quarkus version 999-SNAPSHOT
Build everything:
mvn clean install -DskipTests
Build the native executable the main integration test :
Output of
uname -a
orver
Linux
Output of
java -version
11
GraalVM version (if different from Java)
22.1
Quarkus version or git rev
main
Build tool (ie. output of
mvnw --version
orgradlew --version
)Maven 3.8
Additional information
The repo uses a Google provided native image support library: https://github.com/GoogleCloudPlatform/native-image-support-java
The text was updated successfully, but these errors were encountered: