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: org.apache.lucene.search.TestNumericRangeQuery64 [junit4] Completed in 4251.28s, 34 tests Dawid On Thu, Apr 19, 2012 at 9:28 AM, Dawid Weiss <[email protected]> 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 output. > > 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: [email protected] For additional commands, e-mail: [email protected]
