lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Uwe Schindler" <>
Subject RE: Test failures are out of control......
Date Wed, 21 Feb 2018 23:20:14 GMT
Hey Yonik,

Have you read my e-mail? I just said that there is no need to add another sysprop as its already
there! The default value for the sysprop is just a common-build.xml one-line change.

BTW, as I don't care about Solr tests most of the time, I disabled them completely on my local
machine using in my user's home directory. Every developer can do
the same on his own file (e.g. enable/disable bad apples). Just the
default should be decided here.


Uwe Schindler
Achterdiek 19, D-28357 Bremen

> -----Original Message-----
> From: Yonik Seeley []
> Sent: Thursday, February 22, 2018 12:17 AM
> To: Solr/Lucene Dev <>
> Subject: Re: Test failures are out of control......
> On Wed, Feb 21, 2018 at 6:13 PM, Uwe Schindler <> wrote:
> >> > There are exactly three
> >> > BadApple annotations in the entire code base at present, is there
> >> > enough value in introducing another annotation to make it worthwhile?
> >>
> >> If we change BadApple tests to be executed by default for "ant test"
> >> (but not for the most frequent jenkins jobs), then that would be fine.
> >> Basically, add a -Dtests.disable-badapples and use that for the
> >> jenkins jobs that email the list all the time.
> >
> > No need for a new sysprop. It's already there, just inverted! Configuring
> Jenkins to enable disable them is trivial.
> The issue is that flakey tests should not be ignored by developers
> running unit tests before committing new changes.  That's the most
> important point in time for test coverage.
> -Yonik
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message