.org
> >>> <mailto:dev-unsubscr...@lucene.apache.org>
> >>> For additional commands, e-mail: dev-h...@lucene.apache.org
> >>> <mailto:dev-h...@lucene.apache.org>
> >>>
> >>
> >
> > -
>>> BadApple'd tests.
> >>>
> >>> -
> >>> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> >>> <mailto:dev-unsubscr...@lucene.apache.org>
> >>&g
t; >>> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> >>> For additional commands, e-mail: dev-h...@lucene.apache.org
> >>>
> >>
> >
> > -
> > To unsubscribe, e-mail:
> ---------
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org
>
Begin forwarded message:
> From: Erick Erickson
> Subject: Re: Not adding badappl
Adrien:
"Do you know whether there is something that makes these jobs any different?"
Unfortunately no. I'm not really very well versed in the various test
environments, maybe Uwe or Steve Rowe or Hoss might have some insight?
On Mon, Jun 4, 2018 at 3:34 AM, Adrien Grand wrote:
> Thanks for
Thanks for helping on this front Erick. I noticed a significant decrease in
noise since you started badapple-ing bad tests, but I'm observing that our
smoke-release builds still keep failing because of Solr tests (10 out of
the last 10 builds) in spite of the fact that they disable bad apples:
-
With the long weekend and the fact that the number of non-BadApple
tests is fairly small this week, I'll skip adding more BadApple tests
until next week.
We're scarily close to the non-BaApple'd tests coming under control.
If we're lucky, we can draw a line in the sand soon then start working
on
