This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-11-05
Channels
- # announcements (5)
- # beginners (49)
- # boot (9)
- # calva (34)
- # cider (9)
- # clara (18)
- # clj-kondo (1)
- # cljsrn (7)
- # clojure (196)
- # clojure-dev (4)
- # clojure-europe (11)
- # clojure-france (3)
- # clojure-nl (13)
- # clojure-norway (2)
- # clojure-spec (8)
- # clojure-uk (85)
- # clojurescript (87)
- # clojurex (202)
- # core-logic (6)
- # data-science (6)
- # datomic (9)
- # dirac (1)
- # duct (93)
- # emacs (9)
- # events (1)
- # fulcro (22)
- # hoplon (30)
- # jackdaw (10)
- # keechma (1)
- # leiningen (5)
- # malli (17)
- # off-topic (9)
- # other-languages (3)
- # pedestal (7)
- # re-frame (3)
- # reagent (5)
- # reitit (9)
- # remote-jobs (6)
- # rewrite-clj (80)
- # ring (2)
- # shadow-cljs (191)
- # tools-deps (54)
- # vim (14)
- # xtdb (7)
So I ran my own leinigen build to debug and determined it was failing at eval.sh, which runs a java command. I ran that java command with -verbose flag and it gave me a little more info. the build is hanging when [class, load] is occurring. it loads 4 in reasonable time but each class load after takes significantly more time [12.521 s, 12.521 s, 13.109 s, 13.308 s, 41.109 s, 191.967 s, 431.966s, 10338.197 s, 12491.966 s]
i also tried many different jvm versions just to rule that out, but the same issue. on the bright side im a little more familiar with leinigen internals
i did test with a blank project with the parent dependency that the class load was slow on and it seems to be related to that dependency. so at least i narrowed it down. it is kind of odd that it continues to "work" (no printed errors) but it just takes several hours for each one.