Closed TharmiganK closed 11 months ago
Hi @TharmiganK,
Thanks for raising this! According to the two build outputs, the builds used either Oracle GraalVM:
Java version: 17.0.9+11-LTS, vendor version: Oracle GraalVM 17.0.9+11.1
or GraalVM CE:
Java version: 17.0.9+9, vendor version: GraalVM CE 17.0.9+9.1
.
Since Oracle GraalVM performs additional optimizations, I believe the underlying issue could be a compiler bug. Let me raise this internally with our team.
Thanks for the prompt reply 🙂
Have you tried building with Oracle GraalVM and java-version: '21'
yet? Would be interesting to know whether it's failing in the same way there.
Have you tried building with Oracle GraalVM and
java-version: '21'
yet? Would be interesting to know whether it's failing in the same way there.
Not yet, there is no immediate plan to test with Java 21. Will let you know if we did
Ok, so it turns out we already know about the problem and fixed it on master. The patch will be included in the 17.0.10
CPU release due on January 16, 2023.
Hi @fniephaus,
We have a workflow which use the
setup-graalvm
action to run some tests in GraalVM mode. We have recently migrate that to Java 17:With the above configurations the build is failing with this error:
Complete log can be found here: https://github.com/ballerina-platform/module-ballerinax-health.fhir.r4/actions/runs/7137931179/job/19438661771#step:8:12462
But when we change the distribution to
GraalVM Community Edition
then the build got passed:The passing workflow run: https://github.com/ballerina-platform/module-ballerinax-health.fhir.r4/actions/runs/7138771300/job/19440891466#step:8:12472
I have not tried to reproduce this locally as the build goes OOM in my machine. Appreciate any input on this