graalvm

Discuss GraalVM related topics. Use clojure 1.10.2 or newer for all new projects. Contribute to https://github.com/clj-easy/graal-docs and https://github.com/BrunoBonacci/graalvm-clojure. GraalVM slack: https://www.graalvm.org/slack-invitation/.
Crispin 2020-04-17T16:33:51.136100Z

I have new issues with latest 20.1.0-dev CE graalvm native-image builds

Crispin 2020-04-17T16:34:00.136300Z

https://github.com/oracle/graal/issues/2358

Eugen 2020-04-18T09:19:23.139900Z

are there some integration tests, gradle clojure tck or a clojure stakeholder on the graal side ?

borkdude 2020-04-18T09:36:13.140300Z

I wish

Crispin 2020-04-17T16:34:26.136900Z

Has anyone else seen this behavoir?

borkdude 2020-04-17T17:07:33.137Z

I see a lot of > Error: Frame states being merged are incompatible: unbalanced monitors - locked objects do not match This frame state: [locals: [1,2,3,1,,] stack: [7] locks: [] rethrowException] kind of errors. Are you using clojure 1.10.2-alpha1?

Crispin 2020-04-17T17:41:36.137300Z

yeah I upgraded and tried again

Crispin 2020-04-17T17:41:39.137500Z

same thing

Crispin 2020-04-17T17:47:48.137700Z

I have changed my build script to use an older version of graal 20.1.0-dev Im hosting myself. And it's working.

Crispin 2020-04-17T17:51:56.137900Z

was earlier clojures causing those lock mismatch errors?

Crispin 2020-04-17T17:52:02.138100Z

maybe I will try again tomorrow

borkdude 2020-04-17T18:22:46.138300Z

well, GraalVM was having issues clojure's locking macro earlier, but this is supposed to be fixed in clojure 1.10.2-alpha1. however, libraries AOTed with an earlier version may still exhibit problems

borkdude 2020-04-17T18:23:18.138500Z

or if they are changing GraalVM to frown upon Clojure's new locking macro, we could have another issue, which I hope not!

borkdude 2020-04-17T20:02:27.139200Z

@retrogradeorbit I see a similar NPE with babashka and posted it in the issue

1👍