[GitHub] couchdb-fauxton pull request: travis: notify about broken build
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 feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] couchdb-fauxton pull request: travis: notify about broken build
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/robertkowalski/couchdb-fauxton travis-notification Alternatively you can review and apply these changes as the patch at: https://github.com/apache/couchdb-fauxton/pull/236.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #236 commit 15b869ffa2842149a6207d8ae8f6ebe170881189 Author: Robert Kowalski robertkowal...@apache.org Date: 2015-01-19T13:57:53Z travis: notify about broken build notify #couchdb-dev about a broken build --- 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 feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] couchdb-fauxton pull request: travis: notify about broken build
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 feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
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
Broken build
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.
