The hprof is there:
https://builds.apache.org/hudson/job/Lucene-trunk/ws/checkout/lucene/build/

I am working on a completely separate dir for the hprofs (where I also gzip
them), so Jenkins can pick them up as "artifacts" and archive them. Using
this technique its easier for us to pick up the ones from half hourly
builds.

Uwe

-----
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: [email protected]


> -----Original Message-----
> From: Michael McCandless [mailto:[email protected]]
> Sent: Sunday, May 01, 2011 12:46 PM
> To: [email protected]
> Subject: Re: [HUDSON] Lucene-trunk - Build # 1547 - Failure
> 
> OOME
> 
> Mike
> 
> http://blog.mikemccandless.com
> 
> 
> 
> On Sat, Apr 30, 2011 at 10:43 PM, Apache Jenkins Server
> <[email protected]> wrote:
> > Build: https://builds.apache.org/hudson/job/Lucene-trunk/1547/
> >
> > 1 tests failed.
> > REGRESSION:  org.apache.lucene.index.TestNRTThreads.testNRTThreads
> >
> > Error Message:
> > Some threads threw uncaught exceptions!
> >
> > Stack Trace:
> > junit.framework.AssertionFailedError: Some threads threw uncaught
> exceptions!
> >        at
> >
> org.apache.lucene.util.LuceneTestCase$LuceneTestCaseRunner.runChild(Lu
> > ceneTestCase.java:1246)
> >        at
> >
> org.apache.lucene.util.LuceneTestCase$LuceneTestCaseRunner.runChild(Lu
> > ceneTestCase.java:1175)
> >        at
> >
> org.apache.lucene.util.LuceneTestCase.tearDown(LuceneTestCase.java:535
> > )
> >
> >
> >
> >
> > Build Log (for compile errors):
> > [...truncated 11917 lines...]
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [email protected] For
> > additional commands, e-mail: [email protected]
> >
> >
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected] For additional
> commands, e-mail: [email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to