Apparently the initial ejson commit has been building on our build-bot
instance for about four days. The commit info can be found at [1].
Bottom line is that something hit an infinite loop spewing:

    sed: couldn't flush stdout: Broken pipe

Don't bother trying to read the stdio log, its 44M of that message repeated.

Has anyone noticed this locally? Is this just a transient thing that
was caused by our mucking around in the build system?


[1] http://ci.apache.org/builders/couchdb-coverage/builds/497

Reply via email to