This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-11-02
Channels
- # announcements (2)
- # babashka (10)
- # beginners (61)
- # calva (17)
- # cider (27)
- # clj-kondo (14)
- # clojure (230)
- # clojure-austin (4)
- # clojure-europe (17)
- # clojure-france (6)
- # clojure-hungary (3)
- # clojure-norway (30)
- # clojure-sweden (9)
- # clojure-uk (2)
- # clojurescript (58)
- # conjure (11)
- # core-async (7)
- # cursive (74)
- # datalog (2)
- # datomic (15)
- # events (8)
- # figwheel-main (5)
- # fulcro (2)
- # graalvm (23)
- # graphql (2)
- # helix (17)
- # humbleui (2)
- # jobs (2)
- # kaocha (6)
- # lsp (19)
- # malli (7)
- # nbb (51)
- # off-topic (33)
- # pathom (26)
- # pedestal (2)
- # polylith (1)
- # portal (4)
- # re-frame (17)
- # react (3)
- # reitit (5)
- # releases (2)
- # remote-jobs (2)
- # shadow-cljs (18)
- # sql (65)
- # tools-deps (8)
- # xtdb (28)
What are the potential causes of this error when running tests from my repl?
Failed loading tests:
Exception: java.lang.NullPointerException: null
at java.util.concurrent.ConcurrentHashMap.get (ConcurrentHashMap.java:936)
...
kaocha.type.ns$eval87218$fn__87219.invoke (ns.clj:34)
...
kaocha.testable$load.invokeStatic (testable.clj:94)
kaocha.testable$load.invoke (testable.clj:75)
kaocha.testable$load_testables.invokeStatic (testable.clj:152)
kaocha.testable$load_testables.invoke (testable.clj:144)
kaocha.load$load_test_namespaces.invokeStatic (load.clj:49)
kaocha.load$load_test_namespaces.doInvoke (load.clj:37)
I don't think I'm doing anything special but maybe I amI restarted my repl and it went away so I'm confused what could have caused it.
Hmm, can you share the whole stack trace in case it becomes necessary (if you still have it)?
Sadly, I don't. I should have captured the whole thing, I'm not sure why I didn't. I'll keep an eye out for it happening again
Looking into it more, I'm not sure. It might be caused by keeping some configuration around and then renaming the test's source files
That's fairly early in the process of loading tests, so it could be a bug in clojure.test or Clojure itself.
👍 1