Sorry for all the noise. I think it may be a botched backport of the
timeout support I did yesterday. Will look at it today
oh, hossman fixed this already in SOLR-3335.
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
On Tue, Apr 10, 2012 at 12:32 AM, Uwe Schindler wrote:
> The difference in the nightly builds is -Dtests.nightly=true and
> -Dtests.multiplier=5
>
> Maybe that's related here?
I think it is. The build fails here locally almost every time when I run:
ant test -Dtestcase=TestDistributedSearch
-Dte
hossman_luc...@fucit.org]
> Sent: Monday, April 09, 2012 10:41 PM
> To: dev@lucene.apache.org; yo...@lucidimagination.com
> Subject: Re: nightly build failures
>
>
> : I've noticed our jenkins nightly build pretty much always fails
> : recently (only 2 successes on the whol
: I've noticed our jenkins nightly build pretty much always fails
: recently (only 2 successes on the whole page)
: https://builds.apache.org/job/Solr-trunk/
most of the recent full nightly build failures are because
TestDistributedSearch.testDistribSearch fails in that build, (but not in
I've noticed our jenkins nightly build pretty much always fails
recently (only 2 successes on the whole page)
https://builds.apache.org/job/Solr-trunk/
while the normal tests pretty much always pass (only 2 failures on the
whole page)
https://builds.apache.org/job/Lucene-Solr-tests-only-trunk/
Any
On Sun, Jan 23, 2011 at 1:25 PM, Uwe Schindler wrote:
> Hi,
>
> As said before: There is now a new Hudson version installed and since that
> event no more Clover problems. So let's give it a few days to settle and
> find out if maybe the problem is solved. But even if it's solved, I would
> not cl
t of shutting off the Clover build?
>
> Mike
>
> On Sun, Jan 23, 2011 at 4:30 AM, Uwe Schindler wrote:
> > We had no more nightly build failures since hudson update that were
> > caused by clover. The recent ones are not caused by that, they are
> > caused by a co
no more nightly build failures since hudson update that were caused
> by clover. The recent ones are not caused by that, they are caused by a
> committed "nocommit" by Shaie :-)
>
> Uwe
>
> -
> Uwe Schindler
> H.-H.-Meier-Allee 63, D-28213 Bremen
> htt
We had no more nightly build failures since hudson update that were caused
by clover. The recent ones are not caused by that, they are caused by a
committed "nocommit" by Shaie :-)
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@t
Heh - I'm with you - I think it would be awesome to fix :) I think the other
devs think so too. I think that you prodding the issue is a smart move. We do
want to encourage users to use the nightlies - lets more people try out Uwe's
questionable code early on ;) - fake failures are a downer thou
Sorry, as I said, the last 5 builds are broken by me. and please don't bug me,
Steven and me do our best to serve you good builds nightly. Also the
everybody-especially-some-people-hated haven builds.
And just to mention: the last builds since Hudson upgrade did not fail because
of clover, only
RANT WARNING! RANT WARNING!
When did Lucid enter the picture? This has nothing to do with Lucid.
As you say this may all be taken care of with the new Hudson, and that could
be the end of the story, hooray! I'm perfectly willing to wait and see
if it settles out.
What this *does* have to do
The failures from today are just test builds.
Today also a new Hudson was installed... so please simply wait a few days until
it settles.
If Lucid wants their customer to use nightly builds, they could setup ones on
their servers for their customers? For us Hudson mostly a test system to check
I don't know what other issues you're referring to, but please, please,
please do whatever you can to remove "false failures". It's highly
disconcerting to folks we talk to on the message boards to say
"Functionality you need is in the nightly builds and you can use them, but
just ignore the error
Clover causes Hudson nightly builds to fail intermittently. This is bad,
because it looks like Lucene/Solr tests are failing when they are not. But
Clover is good, so nobody wants to turn it off.
One possible solution (apologies if this has already been suggested): make new
nightly Clover-onl
16 matches
Mail list logo
