Github user garrensmith commented on the pull request:
https://github.com/apache/couchdb-fauxton/pull/236#issuecomment-70496410
+1
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
GitHub user robertkowalski opened a pull request:
https://github.com/apache/couchdb-fauxton/pull/236
travis: notify about broken build
notify #couchdb-dev about a broken build
You can merge this pull request into a Git repository by running:
$ git pull https://github.com
Github user asfgit closed the pull request at:
https://github.com/apache/couchdb-fauxton/pull/236
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the
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
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
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
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
