This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-03-29
Channels
- # announcements (7)
- # asami (13)
- # babashka (22)
- # beginners (52)
- # calva (95)
- # clj-kondo (14)
- # cljs-dev (7)
- # clojars (5)
- # clojure (94)
- # clojure-austin (5)
- # clojure-dev (15)
- # clojure-europe (25)
- # clojure-nl (18)
- # clojure-uk (15)
- # clojuredesign-podcast (28)
- # clojurescript (63)
- # copenhagen-clojurians (1)
- # cursive (3)
- # datalevin (7)
- # datascript (13)
- # datomic (13)
- # duct (14)
- # emacs (24)
- # events (1)
- # fulcro (13)
- # graphql (7)
- # kaocha (4)
- # lambdaisland (6)
- # lsp (22)
- # music (5)
- # off-topic (24)
- # rdf (1)
- # re-frame (3)
- # reitit (9)
- # shadow-cljs (23)
- # sql (15)
- # testing (4)
- # tools-build (6)
- # vim (7)
- # vscode (7)
- # xtdb (21)
Hi, I have a pretty basic kaocha setup which is working well for my needs. I am now setting up automated deployment, and am building my project using github actions. As part of this, my tests run. Right now I’m in the process of getting a database running, but the way kaocha is printing logs is causing me problems in the github environment. As it stands, my tests are crashing (as expected - I don’t have a db set up yet), but kaocha doesn’t print the actual error to stdout/stderr - instead I get a message saying
<test-ns-name>-testExecution error (ConnectException) at
Connection refused (Connection refused)
Full report at:
/var/folders/bh/094hxw3x4bx4msfv9n9jz6580000gn/T/clojure-6044869877193583808.edn
…with the report in the edn file. This has worked fine so far, but it doesn’t work in github actions as I don’t have access to the filesystem for ad-hoc files like this. How do I configure kaocha to print the data it currently spits into the .edn file onto stdout/stderr so github actions can see it and I can evaluate it?
Thanks in advance.
I don’t think this is Kaocha producing the edn
file, but the clojure tooling (`tools.deps`?) that just dumps exceptions.
On a side note: Kaocha does print all output to stdout if a test fails. There is also --no-capture-output
if you want to print output for passed tests too