You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by Stack <st...@duboce.net> on 2014/10/26 03:58:37 UTC
Jenkins log
Lets keep a running notice of changes made up on jenkins here on this
thread.
I just changed branch-1 removing:
-Dmaven.test.redirectTestOutputToFile=true
Internal tests have been passing. They didn't have the above in place.
branch-1 has been passing since we changed logging to WARN level only.
I'll let the above config sit awhile and then put back branch-1 to DEBUG
level.
St.Ack
Re: Jenkins log
Posted by Stack <st...@duboce.net>.
Removed the -Dsurefire.secondPartThreadCount=2 from the trunk build too (so
not branch-1 and trunk run with 5 concurrent threads)
St.Ack
On Thu, Nov 6, 2014 at 9:59 PM, Stack <st...@duboce.net> wrote:
> Removed -Dsurefire.secondPartThreadCount=2 from the branch-1 builds. Now
> we run thread count of 5, the default. Test completes 3 minutes faster (1hr
> 13min rather than 1hr 16min). Will let it soak a while.
>
> On precommits, set -Dsurefire.rerunFailingTestsCount=2 so we retry any
> test that fails (if it completes, reported as flakey). Lets see how this
> does a while.
>
> St.Ack
>
> On Tue, Oct 28, 2014 at 2:31 PM, Stack <st...@duboce.net> wrote:
>
>> Dima Spivak has been digging in on our build fails (with help from Andrew
>> Bayer of Apache on the backend).
>>
>> I changed our build machines to be the below:
>>
>> (ubuntu||Hadoop) && !jenkins-cloud-4GB && !H11
>>
>> ... which is a pool of 16 nodes.
>>
>> From 'ubuntu' (9 nodes) or 'ubuntu||Hadoop' (19 possible nodes).
>>
>> Dima watching branch-1 has figured H11 is sick. And with Andrew's help,
>> they've figured that jenkins-cloud-4GB stuff ain't hefty enough to do out
>> builds.
>>
>> St.Ack
>>
>>
>>
>> On Sun, Oct 26, 2014 at 8:52 PM, Stack <st...@duboce.net> wrote:
>>
>>> I put the config
>>>
>>> -Dmaven.test.redirectTestOutputToFile=true
>>>
>>> back on the branch-1 builds and set log level back to WARN.
>>>
>>> It look like the -D param had no effect. Something to do w/ log amount.
>>> See HBASE-12285.
>>>
>>> St.Ack
>>>
>>> On Sun, Oct 26, 2014 at 4:21 PM, Stack <st...@duboce.net> wrote:
>>>
>>>> I reenabled logging at DEBUG level on branch-1 builds up on jenkins
>>>> (HBASE-12285).
>>>> St.Ack
>>>>
>>>> On Sat, Oct 25, 2014 at 7:58 PM, Stack <st...@duboce.net> wrote:
>>>>
>>>>> Lets keep a running notice of changes made up on jenkins here on this
>>>>> thread.
>>>>>
>>>>> I just changed branch-1 removing:
>>>>>
>>>>> -Dmaven.test.redirectTestOutputToFile=true
>>>>>
>>>>> Internal tests have been passing. They didn't have the above in place.
>>>>> branch-1 has been passing since we changed logging to WARN level only.
>>>>> I'll let the above config sit awhile and then put back branch-1 to DEBUG
>>>>> level.
>>>>>
>>>>> St.Ack
>>>>>
>>>>
>>>>
>>>
>>
>
Re: Jenkins log
Posted by Sean Busbey <bu...@cloudera.com>.
In the precommits job, I removed the svn-cmd argument from the test-patch
invocation. With that the build should be lined up with HBASE-12515.
On Thu, Nov 6, 2014 at 11:59 PM, Stack <st...@duboce.net> wrote:
> Removed -Dsurefire.secondPartThreadCount=2 from the branch-1 builds. Now we
> run thread count of 5, the default. Test completes 3 minutes faster (1hr
> 13min rather than 1hr 16min). Will let it soak a while.
>
> On precommits, set -Dsurefire.rerunFailingTestsCount=2 so we retry any test
> that fails (if it completes, reported as flakey). Lets see how this does a
> while.
>
> St.Ack
>
> On Tue, Oct 28, 2014 at 2:31 PM, Stack <st...@duboce.net> wrote:
>
> > Dima Spivak has been digging in on our build fails (with help from Andrew
> > Bayer of Apache on the backend).
> >
> > I changed our build machines to be the below:
> >
> > (ubuntu||Hadoop) && !jenkins-cloud-4GB && !H11
> >
> > ... which is a pool of 16 nodes.
> >
> > From 'ubuntu' (9 nodes) or 'ubuntu||Hadoop' (19 possible nodes).
> >
> > Dima watching branch-1 has figured H11 is sick. And with Andrew's help,
> > they've figured that jenkins-cloud-4GB stuff ain't hefty enough to do out
> > builds.
> >
> > St.Ack
> >
> >
> >
> > On Sun, Oct 26, 2014 at 8:52 PM, Stack <st...@duboce.net> wrote:
> >
> >> I put the config
> >>
> >> -Dmaven.test.redirectTestOutputToFile=true
> >>
> >> back on the branch-1 builds and set log level back to WARN.
> >>
> >> It look like the -D param had no effect. Something to do w/ log amount.
> >> See HBASE-12285.
> >>
> >> St.Ack
> >>
> >> On Sun, Oct 26, 2014 at 4:21 PM, Stack <st...@duboce.net> wrote:
> >>
> >>> I reenabled logging at DEBUG level on branch-1 builds up on jenkins
> >>> (HBASE-12285).
> >>> St.Ack
> >>>
> >>> On Sat, Oct 25, 2014 at 7:58 PM, Stack <st...@duboce.net> wrote:
> >>>
> >>>> Lets keep a running notice of changes made up on jenkins here on this
> >>>> thread.
> >>>>
> >>>> I just changed branch-1 removing:
> >>>>
> >>>> -Dmaven.test.redirectTestOutputToFile=true
> >>>>
> >>>> Internal tests have been passing. They didn't have the above in place.
> >>>> branch-1 has been passing since we changed logging to WARN level
> only.
> >>>> I'll let the above config sit awhile and then put back branch-1 to
> DEBUG
> >>>> level.
> >>>>
> >>>> St.Ack
> >>>>
> >>>
> >>>
> >>
> >
>
--
Sean
Re: Jenkins log
Posted by Stack <st...@duboce.net>.
Removed -Dsurefire.secondPartThreadCount=2 from the branch-1 builds. Now we
run thread count of 5, the default. Test completes 3 minutes faster (1hr
13min rather than 1hr 16min). Will let it soak a while.
On precommits, set -Dsurefire.rerunFailingTestsCount=2 so we retry any test
that fails (if it completes, reported as flakey). Lets see how this does a
while.
St.Ack
On Tue, Oct 28, 2014 at 2:31 PM, Stack <st...@duboce.net> wrote:
> Dima Spivak has been digging in on our build fails (with help from Andrew
> Bayer of Apache on the backend).
>
> I changed our build machines to be the below:
>
> (ubuntu||Hadoop) && !jenkins-cloud-4GB && !H11
>
> ... which is a pool of 16 nodes.
>
> From 'ubuntu' (9 nodes) or 'ubuntu||Hadoop' (19 possible nodes).
>
> Dima watching branch-1 has figured H11 is sick. And with Andrew's help,
> they've figured that jenkins-cloud-4GB stuff ain't hefty enough to do out
> builds.
>
> St.Ack
>
>
>
> On Sun, Oct 26, 2014 at 8:52 PM, Stack <st...@duboce.net> wrote:
>
>> I put the config
>>
>> -Dmaven.test.redirectTestOutputToFile=true
>>
>> back on the branch-1 builds and set log level back to WARN.
>>
>> It look like the -D param had no effect. Something to do w/ log amount.
>> See HBASE-12285.
>>
>> St.Ack
>>
>> On Sun, Oct 26, 2014 at 4:21 PM, Stack <st...@duboce.net> wrote:
>>
>>> I reenabled logging at DEBUG level on branch-1 builds up on jenkins
>>> (HBASE-12285).
>>> St.Ack
>>>
>>> On Sat, Oct 25, 2014 at 7:58 PM, Stack <st...@duboce.net> wrote:
>>>
>>>> Lets keep a running notice of changes made up on jenkins here on this
>>>> thread.
>>>>
>>>> I just changed branch-1 removing:
>>>>
>>>> -Dmaven.test.redirectTestOutputToFile=true
>>>>
>>>> Internal tests have been passing. They didn't have the above in place.
>>>> branch-1 has been passing since we changed logging to WARN level only.
>>>> I'll let the above config sit awhile and then put back branch-1 to DEBUG
>>>> level.
>>>>
>>>> St.Ack
>>>>
>>>
>>>
>>
>
Re: Jenkins log
Posted by Stack <st...@duboce.net>.
Dima Spivak has been digging in on our build fails (with help from Andrew
Bayer of Apache on the backend).
I changed our build machines to be the below:
(ubuntu||Hadoop) && !jenkins-cloud-4GB && !H11
... which is a pool of 16 nodes.
>From 'ubuntu' (9 nodes) or 'ubuntu||Hadoop' (19 possible nodes).
Dima watching branch-1 has figured H11 is sick. And with Andrew's help,
they've figured that jenkins-cloud-4GB stuff ain't hefty enough to do out
builds.
St.Ack
On Sun, Oct 26, 2014 at 8:52 PM, Stack <st...@duboce.net> wrote:
> I put the config
>
> -Dmaven.test.redirectTestOutputToFile=true
>
> back on the branch-1 builds and set log level back to WARN.
>
> It look like the -D param had no effect. Something to do w/ log amount.
> See HBASE-12285.
>
> St.Ack
>
> On Sun, Oct 26, 2014 at 4:21 PM, Stack <st...@duboce.net> wrote:
>
>> I reenabled logging at DEBUG level on branch-1 builds up on jenkins
>> (HBASE-12285).
>> St.Ack
>>
>> On Sat, Oct 25, 2014 at 7:58 PM, Stack <st...@duboce.net> wrote:
>>
>>> Lets keep a running notice of changes made up on jenkins here on this
>>> thread.
>>>
>>> I just changed branch-1 removing:
>>>
>>> -Dmaven.test.redirectTestOutputToFile=true
>>>
>>> Internal tests have been passing. They didn't have the above in place.
>>> branch-1 has been passing since we changed logging to WARN level only.
>>> I'll let the above config sit awhile and then put back branch-1 to DEBUG
>>> level.
>>>
>>> St.Ack
>>>
>>
>>
>
Re: Jenkins log
Posted by Stack <st...@duboce.net>.
I put the config
-Dmaven.test.redirectTestOutputToFile=true
back on the branch-1 builds and set log level back to WARN.
It look like the -D param had no effect. Something to do w/ log amount. See
HBASE-12285.
St.Ack
On Sun, Oct 26, 2014 at 4:21 PM, Stack <st...@duboce.net> wrote:
> I reenabled logging at DEBUG level on branch-1 builds up on jenkins
> (HBASE-12285).
> St.Ack
>
> On Sat, Oct 25, 2014 at 7:58 PM, Stack <st...@duboce.net> wrote:
>
>> Lets keep a running notice of changes made up on jenkins here on this
>> thread.
>>
>> I just changed branch-1 removing:
>>
>> -Dmaven.test.redirectTestOutputToFile=true
>>
>> Internal tests have been passing. They didn't have the above in place.
>> branch-1 has been passing since we changed logging to WARN level only.
>> I'll let the above config sit awhile and then put back branch-1 to DEBUG
>> level.
>>
>> St.Ack
>>
>
>
Re: Jenkins log
Posted by Stack <st...@duboce.net>.
I reenabled logging at DEBUG level on branch-1 builds up on jenkins
(HBASE-12285).
St.Ack
On Sat, Oct 25, 2014 at 7:58 PM, Stack <st...@duboce.net> wrote:
> Lets keep a running notice of changes made up on jenkins here on this
> thread.
>
> I just changed branch-1 removing:
>
> -Dmaven.test.redirectTestOutputToFile=true
>
> Internal tests have been passing. They didn't have the above in place.
> branch-1 has been passing since we changed logging to WARN level only.
> I'll let the above config sit awhile and then put back branch-1 to DEBUG
> level.
>
> St.Ack
>