Fork me on GitHub
#planck
<
2016-11-04
>
johanatan03:11:58

anyone else seeing this?

Jonathans-MacBook-Pro:planck jonathan$ script/test-all-c 
Running unit tests...
Running integration tests...
Running integration tests...
462c462
< Only :as alias, :refer (names) and :rename {from to} options supported in :require; offending spec: [foo.bar :quu] at line 1 
---
> Only :as alias and :refer (names) options supported in :require; offending spec: [foo.bar :quu] at line 1 

Integration tests have failed.

mfikes03:11:37

@johanatan You may need to run script/clean so that it builds a new ClojureScript compiler

mfikes03:11:17

(I suspect that because the error message diff refers to some stuff present in the newer compiler releases.)

johanatan03:11:54

could failure to run clean also produce a planck binary that isn't kosher?

mfikes03:11:50

Yeah… I’d have to check but clean may use Planck itself, which is probably a bad idea in hindsight

johanatan03:11:53

after building HEAD on planck-c, i tried planck with my screencap script and it seemed to just hang indefinitely (without printing anything). Initial debugging indicated that the main thread was in block_until_timers_complete

johanatan03:11:14

which would imply that there was a SUCCESS returned back to main

johanatan03:11:33

[ahh, yea, I just brew installed --HEAD to get a working 'planck' for the clean lol 🙂 ]

mfikes03:11:52

Yes, I’ve done that. It is silly to have to install planck to clean itself. Ugh.

mfikes03:11:23

Perhaps I’ll revise some of Planck’s build scripts to not use Planck.

johanatan19:11:51

@mfikes do you think it is a good idea for processes started with sh to inherit the pgid of planck itself?

johanatan19:11:17

[i'm occassionally seeing runaway processes and it would be nice to be able to kill them all in one fell swoop]

mfikes19:11:42

No clue. I wonder if Clojure’s sh impl behaves that way.

mfikes19:11:10

What you suggests seems to make sense.

johanatan19:11:22

well, i can't see how it would hurt anything and having it that way would make the use case above nicer