This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-06-27
Channels
- # announcements (1)
- # babashka (2)
- # beginners (64)
- # cider (1)
- # cljs-dev (49)
- # cljsrn (2)
- # clojure (49)
- # clojure-europe (3)
- # clojure-norway (1)
- # clojure-spec (7)
- # clojurescript (116)
- # conjure (3)
- # cursive (4)
- # datomic (1)
- # emacs (2)
- # fulcro (15)
- # graalvm (10)
- # kaocha (1)
- # leiningen (4)
- # meander (1)
- # music (1)
- # off-topic (7)
- # re-frame (37)
- # reagent (3)
- # releases (1)
- # rewrite-clj (6)
- # sci (4)
- # shadow-cljs (16)
- # sql (8)
- # tools-deps (16)
- # xtdb (5)
@borkdude, before I explore your idea further of testing rewrite-cljc under GraalVM > so how it works with babashka: you include the library like the other built-in libraries. and then you run the unit tests from source with bb I vaguely remember you having to get CircleCI to bump available RAM to native-image babashka… am I remembering correctly?
@lee A couple of things to try:
- Set BABASHKA_XMX to -J-Xmx3500m
or something like that and pray it compiles
- Disable all feature flags to eliminate libraries you don't need
- Use sci instead of bb for trying this out. The only other ns you'll need to incorporate is clojure.test, you can copy that code from babashka. The latter could also serve as a template for testing other libs in GraalVM
Or: ask @marc-omorain to bump your memory limit. Or use Github actions, not CircleCI to compile.