This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-12-03
Channels
- # adventofcode (151)
- # asami (34)
- # babashka (43)
- # beginners (111)
- # cider (2)
- # clj-kondo (6)
- # cljdoc (12)
- # clojure (140)
- # clojure-australia (10)
- # clojure-europe (14)
- # clojure-france (5)
- # clojure-gamedev (5)
- # clojure-nl (4)
- # clojure-uk (10)
- # clojurescript (20)
- # community-development (9)
- # conjure (1)
- # core-async (4)
- # cryogen (3)
- # cursive (2)
- # datomic (17)
- # emacs (9)
- # events (1)
- # fulcro (27)
- # juxt (8)
- # kaocha (2)
- # lambdaisland (14)
- # off-topic (23)
- # pathom (37)
- # pedestal (2)
- # re-frame (8)
- # reagent (8)
- # reclojure (9)
- # reitit (5)
- # reveal (34)
- # shadow-cljs (27)
- # spacemacs (10)
- # tools-deps (123)
- # vim (28)
- # xtdb (17)
I did a few attempts with the retry plugin and it still doesn't really work
https://github.com/AndreaCrotti/kaocha-retry/blob/main/src/kaocha/plugin/retry.clj#L32
• it looks like wrap-run runs multiple times even if I just do a single run in theory, which is why I had to add that reported
atom set to keep track of what was already reported
• still as it is now it's not actually reporting anything, even though in theory it should report everything that's not a fail, and report failures only if they failed the max number of times allowed
The only other example of wrap-run I found was capture-output but it's not really similar in a way.
I guess it would be nice to see a full trace of the various hooks when they are running a test, to see exactly the order and what kind of input/output they do