lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dawid Weiss <>
Subject Re: [JENKINS] Lucene-trunk - Build # 1899 - Failure
Date Thu, 19 Apr 2012 07:37:49 GMT
I'll try to inspect later today why these are so slow in that run:

   [junit4] <JUnit4> says g'day! Master seed: C26BAC36B9BF265D

   [junit4] Suite: org.apache.lucene.index.TestByteSlices
   [junit4] Completed in 1852.84s, 1 test

   [junit4] Suite:
   [junit4] Completed in 4251.28s, 34 tests


On Thu, Apr 19, 2012 at 9:28 AM, Dawid Weiss
<> wrote:
>> I have seen this on jenkins several times (especially with Clover instrumentation).
In this case instrumentation was running.
> Clover is a hog, we've experienced that too.
>> I think its caused by too many instrumentation (per statement) in heavy tests like
TestNRQ or similar. Unfortunately we don’t see here, which test exactly was leading to this
> I don't think you'd be able to see that precisely anyway because these
> are printed to two different stream buffers -- it bypasses Java's
> PrintStreams and dumps directly to the original file descriptor.
> Dawid

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

View raw message