cider 2018-07-01 | Slack Archive

lemons12:07:00

Hey. Not sure whether this is cider or spacemacs problem, but since yesterday when I run tests via cider I see no results in minibuffer and dedicated test buffer does not pop up in case there are failed tests. Anyone else having this problem?

(ns cider-test.core-test
  (:require [clojure.test :refer :all]
            [cider-test.core :refer :all]))

(deftest a-test
  (testing "FIXME, I fail."
    (is (= 0 1))))

in messages buffer

Running test a-test in cider-test.core-test...
=> #'cider-test.core-test/a-test

ackerleytng14:07:40

oh yes i'm having this issue too

ackerleytng14:07:52

i thought my test was just taking very long

bozhidar21:07:29

Yesterday supposedly I fixed one issue, but I might have introduced another one.

bozhidar21:07:48

https://github.com/clojure-emacs/cider/issues/2357

bozhidar21:07:39

I don’t have time to debug this for the next few days. Likely one of the nils are removed from the request was actually meaningful to the backend or something like this.

lemons13:07:40

I see. I'll make an issue on github for tracking purposes. Thanks for all your work!

bozhidar21:07:29

> we should have a defvar cider-last-jack-in-command that is set to the command CIDER uses to start the users project. This way when there are errors on jack-in it is easier to see if its CIDER related or not. They can just run it on the command line to see if it works “natively”

bozhidar21:07:24

I was thinking a while back that we can associate this info with the REPL that was created by jack-in.

bozhidar21:07:39

> Yes but I think it truncates sometimes

bozhidar21:07:52

@dpsutton Does it? It should not do this.

2018-07-01

Channels