Open grzm opened 6 years ago
From a first glance, it looks like something happens to the stream opened for reading Clojure in the LispReader.
Because things in boot run concurrently in pods, I feel there is some resource contention going on on the sources or build.boot
itself.
I might be completely off of course :smile:
Just wanted to say that I hit this too, occasionally. The exception is the same, Caused by: java.io.IOException: Stream closed, compiling:(clojure/core_instant18.clj:15:1)
and so on.
It doesn't happen with every project, in fact I have only seen one project yet where this happens (but it happened a few times there already). I use boot-test
to test it and run (clojure.spec.test.alpha/instrument (clojure.spec.test.alpha/enumerate-namespace 'my.namespace))
before running the tests.
Problem Description
When using boot-tools-deps and boot-test, sometimes a
java.lang.ExceptionInInitializerError
will occur after the test has completed.I don't know if this is specific to boot-tools-deps and boot-test, but that's where I came across the error and can reproduce it.
Steps to reproduce
On occassion, I'll get the following stacktrace (a full example is also provided in the repo). Over the course of 10 runs, I'll see it at least twice, if not more often.
Platform details
Boot details
build.boot
present? Yes.~/.boot/profile
present? No. Task name? boot deps -Q testDuplicated from the repo:
build.boot
deps.edn