I'm having a travis failure for a test suite that works locally https://travis-ci.org/leonoel/missionary Does the dump at the end look familiar to someone ?

@leonoel I think it might be possible to get Planck to crash in odd ways if it shuts down while there are threads processing things. (It shouldn't crash, of course, but I think I've seen this before.) So, my first hunch is that there might be a timer in your script that is firing but the script ends, and things derail. Does that sound like it might be a possibility?

Oh, cool, I see your code is open source.

the test suite is full of timers

using cljs.test/async

@leonoel FWIW, it is passing for me locally with lumo

$ clojure -Acljs-test -x lumo

Testing missionary.core-test

Ran 17 tests containing 0 assertions.
0 failures, 0 errors.

I smell a Planck bug.

(To run with lumo, use 3.7.0 of the test runner.)

good to know

Sometimes it runs properly, but sometimes it just terminates

Mikes-iMac:missionary mfikes$ clojure -Acljs-test -x planck

Testing missionary.core-test

Ran 17 tests containing 0 assertions.
0 failures, 0 errors.
Mikes-iMac:missionary mfikes$ clojure -Acljs-test -x planck
Mikes-iMac:missionary mfikes$

Planck will specifically keep the process running if it knows there are outstanding timers.

(Just like Node.)

OK I will try to investigate more. Thanks for your time

@leonoel I can see that the code in Planck that blocks until timers is complete isn't actually blocking. Seeing if I can sort out what that bug might be.

@leonoel Fixed https://github.com/planck-repl/planck/issues/998