Incomplete output

[anotherchrissmith]

I frequently see buck exit before it has finished displaying its output to the console. It might exit in the middle of printing a test's class name for example, leaving the console prompt half way across the screen. This happens intermittently (50% of the time for us) and can be reproduced simply by running buck over and over without making any changes.

In each case, the buck process's result code is 227, which appears to be NAILGUN_CONNECTION_BROKEN (from ng.c), which would explain what's happening.

Does anyone else get this? Can anyone suggest how to investigate?

Thanks

[jimpurbrick]

What does your .buckd/buckd.log say?

[bolinfest]

Are you using 'buck run', by chance?
On Jul 25, 2014 4:01 PM, "Jim Purbrick" [email protected] wrote:

What does your .buckd/buckd.log say?

—
Reply to this email directly or view it on GitHub
#164 (comment).

[anotherchrissmith]

Sorry for the delay, I was away last week. I no longer notice the problem although I have disabled buckd because of this issue #170.

[anotherchrissmith]

Now that #170 appears to have been fixed (brilliant work, thanks), this issue also appears to have been fixed. I can run buck multiple times, over and over, and it now gives me consistent output without aborting half way through. Closing. Thanks.