Re: Broken build
My nightly builds got tripped up on the make distcheck breakage, but seem to work after that got fixed. On 9 Apr 2011, at 02:25, Paul Davis wrote: 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
Re: Broken build
Cool. I'll ignore it for now then. On Apr 9, 2011, at 7:13 AM, Jan Lehnardt j...@apache.org wrote: My nightly builds got tripped up on the make distcheck breakage, but seem to work after that got fixed. On 9 Apr 2011, at 02:25, Paul Davis wrote: 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
Re: Broken build
On Apr 8, 2011, at 8:25 PM, Paul Davis wrote: 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 Cloudant's Jenkins instance is 18 days behind on CouchDB builds, so we didn't notice anything. I haven't had the time to figure out why it stopped pulling changes.
