However, all other things seem to be working correctly, for example if I call run-tests directly in the Quasi-REPL (i.e. the cqc window), that does run the tests and reports test failures as I expect:
(clojure.test/run-tests 'isa2-assembler.disasm-test)
Testing isa2-assembler.disasm-test
hello from disasm/run
FAIL in (test-disassembler-returns-null) (disasm_test.clj:11)
The disassembler entry point returns null
expected: (= nil (run [154]))
actual: (not (= nil 5))
Ran 1 tests containing 1 assertions.
1 failures, 0 errors.
{:test 1, :pass 0, :fail 1, :error 0, :type :summary}
Press ENTER or type command to continue
I have found another person reporting a similar problem here on StackOverflow. Similarly to that SO question, I'm running nrepl in a Docker as well. However, his advice to fiddle with the order of plugins doesn't help me.
I've added a bit of debug logging to s:handle_test_response to inspect what data it gets:
for [mkey, mval] in items(a:message)
echo 'message[' . mkey . '] = ' . mval
endfor
and it seems like it's receiving data in a format it does not expect. Here's what I get in my message trace:
Looking at s:handle_test_response code, it doesn't seem to expect any of these keys, it's looking up something else.
I'm not sure this is a bug in vim-fireplace, could be a problem with my setup, but it manifests in a way that may benefit from some sort of defensive fix. Does this resemble any known problem? How can I debug this further?
Versions of the software I run in the container:
$ clj --version
Clojure CLI version 1.11.1.1200
$ lein version
Leiningen 2.10.0 on Java 11.0.17 OpenJDK 64-Bit Server VM
$ cat .lein/profiles.clj
{:user {:plugins [[cider/cider-nrepl "0.29.0"]]}}
Vim is running on the host, though. Is it possible that vim-fireplace picks up something incompatible from the host machine?
Hi and thanks for making vim-fireplace!
I stumbled upon a curious problem - when I run
:RunTests, fireplace doesn't actually run anything, it fast forwards to reporting success:However, all other things seem to be working correctly, for example if I call
run-testsdirectly in the Quasi-REPL (i.e. thecqcwindow), that does run the tests and reports test failures as I expect:I have found another person reporting a similar problem here on StackOverflow. Similarly to that SO question, I'm running nrepl in a Docker as well. However, his advice to fiddle with the order of plugins doesn't help me.
I've added a bit of debug logging to
s:handle_test_responseto inspect what data it gets:and it seems like it's receiving data in a format it does not expect. Here's what I get in my message trace:
Looking at
s:handle_test_responsecode, it doesn't seem to expect any of these keys, it's looking up something else.I'm not sure this is a bug in vim-fireplace, could be a problem with my setup, but it manifests in a way that may benefit from some sort of defensive fix. Does this resemble any known problem? How can I debug this further?
Versions of the software I run in the container:
Vim is running on the host, though. Is it possible that vim-fireplace picks up something incompatible from the host machine?