Fork me on GitHub
#graalvm
<
2022-01-25
>
ericdallo14:01:22

Graalvm 22.0.0.2, 21.3.1 and 20.3.5 released! https://www.graalvm.org/release-notes/22_0/

🎉 5
borkdude15:01:57

nice. just released bb with 21.3.0, time to upgrade ;)

đź‘Ť 1
lread15:01:22

For those of us that use sdkman, nice that the graal team is now involved here, the new release is already listed.

ericdallo15:01:59

time to bump on #nix :)

ericdallo15:01:36

Any reason to bump our apps to graal 21.3.1 and not 22 ?

lread16:01:11

FWIW, I test that rewrite-clj works when compiled under Graal native-image latest… so for me that means 22.

đź‘Ť 1
lread15:01:27

Curious… are folks building new native images with JDK11 or JDK17 version?

ericdallo15:01:01

clojure-lsp is using 11

borkdude16:01:32

I've contemplated 17 for bb but it didn't add anything pressing and it added 5mb or so to the binary. Also it's not completely unlikely that 17 will contain some issues as it's new so I'll wait a bit with that.

lread16:01:03

I’ve included 11 and 17 to the CI matrix for rewrite-clj… for whatever that is worth!

borkdude16:01:25

I'll upgrade bb to 22 jvm 11 now

lread16:01:17

Sweet petunias! Native image CI is failing on Windows for me! Time to dust off the old VM.

lread16:01:16

(I did also switch to Graal’s setup-graalvm GitHub Action, could be that).

lread16:01:39

Hmm… nice… for users of scoop on Windows… Graalvm v22 is already available.

borkdude17:01:15

3.3mb reduction in image size for bb with graalvm 22 jvm 11

🆒 5
lread17:01:52

Ah… good… in that I don’t have a hard mystery to solve. JDK17 also fails for me on my Windows VM with same symptom as failure on CI. But JDK11 passes on VM. I’ll drop JDK17 from rewrite-clj CI matrix.