Re: Build failed in Jenkins: Lucene-Solr-40-ReleaseSmoke #193

2012-09-26 Thread Robert Muir
-Original Message- >> From: Robert Muir [mailto:rcm...@gmail.com] >> Sent: Wednesday, September 26, 2012 6:22 AM >> To: dev@lucene.apache.org >> Subject: Re: Build failed in Jenkins: Lucene-Solr-40-ReleaseSmoke #193 >> >> Can we improve the way the smoketester works

Re: Build failed in Jenkins: Lucene-Solr-40-ReleaseSmoke #193

2012-09-26 Thread Michael McCandless
12 6:22 AM > To: dev@lucene.apache.org > Subject: Re: Build failed in Jenkins: Lucene-Solr-40-ReleaseSmoke #193 > > Can we improve the way the smoketester works here? > > I've been running lucene's tests in loops for a really long time now > trying to provoke any test fail, but

RE: Build failed in Jenkins: Lucene-Solr-40-ReleaseSmoke #193

2012-09-26 Thread Steven A Rowe
+1 -Original Message- From: Robert Muir [mailto:rcm...@gmail.com] Sent: Wednesday, September 26, 2012 6:22 AM To: dev@lucene.apache.org Subject: Re: Build failed in Jenkins: Lucene-Solr-40-ReleaseSmoke #193 Can we improve the way the smoketester works here? I've been running luc

Re: Build failed in Jenkins: Lucene-Solr-40-ReleaseSmoke #193

2012-09-26 Thread Robert Muir
Can we improve the way the smoketester works here? I've been running lucene's tests in loops for a really long time now trying to provoke any test fail, but now i finally provoked one and we never will know what it is. Instead of 'see /path/to/log' when something fails, can we just cat /path/to/l

Build failed in Jenkins: Lucene-Solr-40-ReleaseSmoke #193

2012-09-26 Thread hudsonseviltwin
See -- [...truncated 41716 lines...] prep-lucene-jars: resolve-example: [echo] Building solr-example... ivy-availability-check: ivy-fail: ivy-configure: [ivy:configure] :: load