This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-01-25
Channels
- # aws (2)
- # bangalore-clj (2)
- # beginners (90)
- # boot (89)
- # bristol-clojurians (1)
- # cider (23)
- # cljs-dev (48)
- # cljsjs (2)
- # cljsrn (3)
- # clojure (118)
- # clojure-argentina (3)
- # clojure-austin (8)
- # clojure-czech (1)
- # clojure-dev (18)
- # clojure-ireland (1)
- # clojure-italy (4)
- # clojure-russia (6)
- # clojure-spec (75)
- # clojure-uk (224)
- # clojurescript (103)
- # core-async (28)
- # cursive (3)
- # datascript (7)
- # datomic (15)
- # dirac (30)
- # emacs (14)
- # events (3)
- # figwheel (1)
- # hispano (1)
- # hoplon (176)
- # lambdaisland (1)
- # lein-figwheel (6)
- # off-topic (21)
- # om (7)
- # onyx (2)
- # pedestal (6)
- # re-frame (4)
- # reagent (15)
- # spacemacs (67)
- # specter (13)
- # testing (9)
- # untangled (65)
- # vim (6)
- # yada (1)
Hi -- has anyone had an issue similar to this: Using boot to run a clj/s test suite on CircleCI (with some clojure.spec tests). When tests fail, CircleCI does not recognize and says tests were successful. I think it's because an exit code of 0 was returned but I'm wondering if there's more going on.
@emergence I had that issue with ClojureScript
if that's your issue, just use @bensu's Doo library
it'll return the correct exit code for CI's
Hi @anmonteiro -- Thanks for responding. I actually just figured it out. Was using crisptrutski/boot-cljs-test
and had to add :exit? true
to my (test-cljs)
call. I believe it uses doo
as a dependency.
@emergence you can have a look at a slightly complex setup here: https://github.com/anmonteiro/lumo/blob/master/build.boot#L36-L52