We've had an integration test that has very occasionally failed since go 1.8.x, which is that a pipe reader appears to be getting closed rather than just giving EOF when the writer is closed. An isolated test case is here in this repository: https://github.com/marksheahan/pipebug, just checkout and run 'make' a few times to reproduce.
The problem only occurs on Linux; I have never reproduced the problem on Darwin. Am I misusing the os/exec.Cmd API somehow? I don't understand what I am doing incorrectly if anything. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
