-
Notifications
You must be signed in to change notification settings - Fork 186
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
FOP integration tests fail in native mode with GraalVM 20.3.0 #2113
Comments
@JiriOndrusek maybe you know the FOP internals better than me. Do you have some time to look into this? |
@jamesnetherton I can look into it tomorrow. Would that be ok? Which branch is it, camel-master? |
Yes, tomorrow is fine. Thanks! You can use the master branch. Bump the Quarkus version to 1.11.0.CR1 and use GraalVM 20.3.0 to reproduce the error. |
I dared to |
Problem is caused by graalvm. There should be an AWT support in graalmvm 20.3, but it didn't make it (see comment Issue is reported on graalvm - oracle/graal#3115 I suppose that we have to wait for the graalvm version, which doesn't contain this bug. |
See also quarkusio/quarkus#13954 where they say that the issue will also be fixed in GraalVM 20.3.1. AFAIK, both GraalVM 21.0.0's and 20.3.1's ETA is after Quarkus 1.11. Building on GraalVM 20.2.0 will perhaps still be possible with Quarkus 1.11 - which could be seen as a workaround for camel-quarkus-fop users. Using Mandrel 20.3.0 (where the issue is fixed too) might be another option. |
Having said that I think this issue is not a blocker for #2111 I'd find it OK, to disable the failing FOP tests until GraalVM 21.0.0 or 20.3.1 is available via Quarkus. |
Agreed - we can always add a release note about it too. |
Both GraalVM 21.0.0 and 20.3.1 are available now and the issue should not occur anymore. |
Quarkus 1.11.0.CR1 bumped GraalVM to 20.3.0. We now see a failure with FOP:
The text was updated successfully, but these errors were encountered: