Re: Split geode nightly build into two jobs

2017-03-14 Thread Darrel Schneider 
+1

On Mon, Mar 13, 2017 at 1:51 PM, Bruce Schuchardt 
wrote:

> +1
>
>
> Le 3/13/2017 à 1:49 PM, Jared Stewart a écrit :
>
>> +1
>>
>> - Jared
>>
>> On Mar 13, 2017, at 1:45 PM, Anthony Baker  wrote:
>>>
>>> We won’t get notifications from successful builds (which should happen
>>> always except for newly introduced issues).
>>>
>>> So you’ll only get notified of flaky test failures.
>>>
>>> ++1
>>>
>>> Anthony
>>>
>>> On Mar 13, 2017, at 1:32 PM, Kirk Lund  wrote:

 Right now the flaky tests are NOT part of the nightly build report.
 However, they can make it fail. At present, if only flaky tests fail,
 then
 it generates errors in console output but the test results page says
 zero
 tests fail. And we always have at least one flaky fail, so we never get
 a
 green build.


 On Mon, Mar 13, 2017 at 12:22 PM, Anilkumar Gingade <
 aging...@pivotal.io>
 wrote:

 I like the idea...But, it will be nice to a single report...When the
> jobs
> are split, there may be tendency to ignore the flaky-test runs
>
> Other option is to: run all non-flaky tests first and then
> flaky-tests...
>
> -Anil.
>
>
> On Mon, Mar 13, 2017 at 10:44 AM, Kirk Lund  wrote:
>
> I'd like to propose splitting the Geode Nightly build into two jobs:
>>
>> 1) precheckin without flakyTest
>> 2) flakyTest by itself
>>
>>
>

Re: Split geode nightly build into two jobs

2017-03-13 Thread Bruce Schuchardt 

+1

Le 3/13/2017 à 1:49 PM, Jared Stewart a écrit :

+1

- Jared


On Mar 13, 2017, at 1:45 PM, Anthony Baker  wrote:

We won’t get notifications from successful builds (which should happen always 
except for newly introduced issues).

So you’ll only get notified of flaky test failures.

++1

Anthony


On Mar 13, 2017, at 1:32 PM, Kirk Lund  wrote:

Right now the flaky tests are NOT part of the nightly build report.
However, they can make it fail. At present, if only flaky tests fail, then
it generates errors in console output but the test results page says zero
tests fail. And we always have at least one flaky fail, so we never get a
green build.


On Mon, Mar 13, 2017 at 12:22 PM, Anilkumar Gingade 
wrote:


I like the idea...But, it will be nice to a single report...When the jobs
are split, there may be tendency to ignore the flaky-test runs

Other option is to: run all non-flaky tests first and then flaky-tests...

-Anil.


On Mon, Mar 13, 2017 at 10:44 AM, Kirk Lund  wrote:


I'd like to propose splitting the Geode Nightly build into two jobs:

1) precheckin without flakyTest
2) flakyTest by itself

Re: Split geode nightly build into two jobs

2017-03-13 Thread Jared Stewart 
+1 

- Jared

> On Mar 13, 2017, at 1:45 PM, Anthony Baker  wrote:
> 
> We won’t get notifications from successful builds (which should happen always 
> except for newly introduced issues).
> 
> So you’ll only get notified of flaky test failures.
> 
> ++1
> 
> Anthony
> 
>> On Mar 13, 2017, at 1:32 PM, Kirk Lund  wrote:
>> 
>> Right now the flaky tests are NOT part of the nightly build report.
>> However, they can make it fail. At present, if only flaky tests fail, then
>> it generates errors in console output but the test results page says zero
>> tests fail. And we always have at least one flaky fail, so we never get a
>> green build.
>> 
>> 
>> On Mon, Mar 13, 2017 at 12:22 PM, Anilkumar Gingade 
>> wrote:
>> 
>>> I like the idea...But, it will be nice to a single report...When the jobs
>>> are split, there may be tendency to ignore the flaky-test runs
>>> 
>>> Other option is to: run all non-flaky tests first and then flaky-tests...
>>> 
>>> -Anil.
>>> 
>>> 
>>> On Mon, Mar 13, 2017 at 10:44 AM, Kirk Lund  wrote:
>>> 
 I'd like to propose splitting the Geode Nightly build into two jobs:
 
 1) precheckin without flakyTest
 2) flakyTest by itself
 
>>> 
>

Re: Split geode nightly build into two jobs

2017-03-13 Thread Anthony Baker 
We won’t get notifications from successful builds (which should happen always 
except for newly introduced issues).

So you’ll only get notified of flaky test failures.

++1

Anthony

> On Mar 13, 2017, at 1:32 PM, Kirk Lund  wrote:
> 
> Right now the flaky tests are NOT part of the nightly build report.
> However, they can make it fail. At present, if only flaky tests fail, then
> it generates errors in console output but the test results page says zero
> tests fail. And we always have at least one flaky fail, so we never get a
> green build.
> 
> 
> On Mon, Mar 13, 2017 at 12:22 PM, Anilkumar Gingade 
> wrote:
> 
>> I like the idea...But, it will be nice to a single report...When the jobs
>> are split, there may be tendency to ignore the flaky-test runs
>> 
>> Other option is to: run all non-flaky tests first and then flaky-tests...
>> 
>> -Anil.
>> 
>> 
>> On Mon, Mar 13, 2017 at 10:44 AM, Kirk Lund  wrote:
>> 
>>> I'd like to propose splitting the Geode Nightly build into two jobs:
>>> 
>>> 1) precheckin without flakyTest
>>> 2) flakyTest by itself
>>> 
>>

Re: Split geode nightly build into two jobs

2017-03-13 Thread Kirk Lund 
Right now the flaky tests are NOT part of the nightly build report.
However, they can make it fail. At present, if only flaky tests fail, then
it generates errors in console output but the test results page says zero
tests fail. And we always have at least one flaky fail, so we never get a
green build.


On Mon, Mar 13, 2017 at 12:22 PM, Anilkumar Gingade 
wrote:

> I like the idea...But, it will be nice to a single report...When the jobs
> are split, there may be tendency to ignore the flaky-test runs
>
> Other option is to: run all non-flaky tests first and then flaky-tests...
>
> -Anil.
>
>
> On Mon, Mar 13, 2017 at 10:44 AM, Kirk Lund  wrote:
>
> > I'd like to propose splitting the Geode Nightly build into two jobs:
> >
> > 1) precheckin without flakyTest
> > 2) flakyTest by itself
> >
>

Re: Split geode nightly build into two jobs

2017-03-13 Thread Anilkumar Gingade 
I like the idea...But, it will be nice to a single report...When the jobs
are split, there may be tendency to ignore the flaky-test runs

Other option is to: run all non-flaky tests first and then flaky-tests...

-Anil.


On Mon, Mar 13, 2017 at 10:44 AM, Kirk Lund  wrote:

> I'd like to propose splitting the Geode Nightly build into two jobs:
>
> 1) precheckin without flakyTest
> 2) flakyTest by itself
>

Re: Split geode nightly build into two jobs

2017-03-13 Thread Dan Smith 
+1

-Dan

On Mon, Mar 13, 2017 at 10:44 AM, Kirk Lund  wrote:

> I'd like to propose splitting the Geode Nightly build into two jobs:
>
> 1) precheckin without flakyTest
> 2) flakyTest by itself
>

Split geode nightly build into two jobs

2017-03-13 Thread Kirk Lund 
I'd like to propose splitting the Geode Nightly build into two jobs:

1) precheckin without flakyTest
2) flakyTest by itself