Build failed in Jenkins: Aurora #627

See Changes: [mchucarroll] Improve handling of unknown errors in the aurora client. -- [...truncated 407 lines...] twitter.common.python: Packaging twitter.common.util :: Installing /tmp/user/2/tmpvbs

Re: Health Check Disabler

Love the idea, thanks for the contribution! Added a comment to the review. -=Bill On Tue, Oct 7, 2014 at 5:00 PM, David Pan wrote: > Hi Aurora, > > I am currently working on a health check disabler for > https://issues.apache.org/jira/browse/AURORA-795 > > Review Board: https://reviews.apache.

Build failed in Jenkins: Aurora #628

See Changes: [kevints] Reject new GC tasks when shutting down -- [...truncated 497 lines...] twitter.common.python.http: Opening (uncached) :: Fetching https://pypi.python.org/packages/source/p/pytest/pyt

Build failed in Jenkins: Aurora #629

See Changes: [mchucarroll] Move the error-log seed file to a user specified directory. -- [...truncated 7870 lines...] SUCCESS:

Re: Build failed in Jenkins: Aurora #629

Bumped into these as well after rebasing https://reviews.apache.org/r/26308 I've rolled cleanups into my change and will be submitting shortly. -=Bill On Wed, Oct 8, 2014 at 11:20 AM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See

Re: Build failed in Jenkins: Aurora #629

Filed https://issues.apache.org/jira/browse/AURORA-818 so we automate the addition of check style into the local git commit hook. On Wed, Oct 8, 2014 at 11:20 AM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See > > Changes: > > [m

Re: Build failed in Jenkins: Aurora #629

Thanks Bill. On Wed, Oct 8, 2014 at 11:28 AM, Bill Farner wrote: > Bumped into these as well after rebasing > https://reviews.apache.org/r/26308 > > I've rolled cleanups into my change and will be submitting shortly. > > -=Bill > > On Wed, Oct 8, 2014 at 11:20 AM, Apache Jenkins Server < > jenk.

Build failed in Jenkins: Aurora #630

See Changes: [mchucarroll] Fix error in incorrect deprecation warning on v1 "ssh" command. -- [...truncated 7880 lines...] SUCCESS:

Re: Build failed in Jenkins: Aurora #630

Mark, Until https://issues.apache.org/jira/browse/AURORA-818 is fixed, could you ensure you've added the checkstyle pre-commit hook? Thanks! Joe On Wed, Oct 8, 2014 at 12:05 PM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See >

Question about JIRA fields

Hey all, We have "Fix Version", "Target Version" and "Affects Version" fields in JIRA. I've got a question - should we always set "Fix Version" to the next upcoming release regardless of whether a bug actually existed in a previous release? For example, https://issues.apache.org/jira/browse/AUROR

Re: Build failed in Jenkins: Aurora #629

This is tracked by https://reviews.apache.org/r/26428/. On Wed, Oct 8, 2014 at 11:31 AM, Joe Smith wrote: > Thanks Bill. > > On Wed, Oct 8, 2014 at 11:28 AM, Bill Farner wrote: > >> Bumped into these as well after rebasing >> https://reviews.apache.org/r/26308 >> >> I've rolled cleanups into my

Build failed in Jenkins: Aurora #631

See Changes: [kevints] Don't kill GC Executor after period of inactivity [kevints] Drop syncrhonized from JobUpdateEventSubscriber -- [...truncated 9403 lines...] SUCCESS:

Re: Question about JIRA fields

Target Version can be used until a release is cut. If we mark all tickets here with the next release, the dev on commit or the release manager can then update the Fix Version for tickets actually in the release. This has been useful on other projects when there are more tickets trying to get out

Jenkins build is back to normal : Aurora #632

See

Build failed in Jenkins: Aurora #633

See Changes: [jcohen] Serve HTTP assets out of a standard classpath root. -- Started by an SCM change Building remotely on ubuntu-1 (docker Ubuntu ubuntu) in workspace

Re: Build failed in Jenkins: Aurora #633

Bill, I think you added code coverage to gradle. Can you check what is going on here? On Wed, Oct 8, 2014 at 1:14 PM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See > > Changes: > > [jcohen] Serve HTTP assets out of a standard cl

Re: Build failed in Jenkins: Aurora #633

Can you? -=Bill On Wed, Oct 8, 2014 at 2:04 PM, Zameer Manji wrote: > Bill, I think you added code coverage to gradle. Can you check what is > going on here? > > On Wed, Oct 8, 2014 at 1:14 PM, Apache Jenkins Server < > jenk...@builds.apache.org> wrote: > >> See

Re: Build failed in Jenkins: Aurora #633

https://issues.apache.org/jira/browse/AURORA-819 On Wed, Oct 8, 2014 at 2:10 PM, Bill Farner wrote: > Can you? > > -=Bill > > On Wed, Oct 8, 2014 at 2:04 PM, Zameer Manji > wrote: > >> Bill, I think you added code coverage to gradle. Can you check what is >> going on here? >> >> On Wed, Oct 8,

Re: Build failed in Jenkins: Aurora #633

I think this is the same flakiness we saw once when I ran this locally. It wasn't repeatable though. On Wed, Oct 8, 2014 at 2:17 PM, Zameer Manji wrote: > https://issues.apache.org/jira/browse/AURORA-819 > > On Wed, Oct 8, 2014 at 2:10 PM, Bill Farner wrote: > >> Can you? >> >> -=Bill >> >> On

Build failed in Jenkins: Aurora #634

See Changes: [wfarner] Fix exit condition for RPC loop, fix test_status_api_failure test. -- Started by an SCM change Building remotely on ubuntu-5 (docker Ubuntu ubuntu5 ubuntu) in workspace

Jenkins build is back to normal : Aurora #635

See