jethrogb
timing bug?
On osx running cargo test the test fails with: rust-reduce: run with initial input did not indicate success
However when I debug through it, it doesn't fail there. Something fishy is going on (or in this case something bashy?)...
(also on the subject of timing, I've not managed to get it to write out any output yet... (aside from it deleting the input file). The WaitGuards are neat, but I wonder if the process ends before the file is flushed or something. Still investigating on that one. (For now I can copy and paste the last intermediate output written to the console..)
From what I understand, you're saying a simple cargo test on OSX doesn't work? Unfortunately I don't have access to an OSX machine so I can't really help debug this.
