Re: Build failed in Hudson: Lucene-trunk #828

2009-05-15 Thread Michael McCandless
On Fri, May 15, 2009 at 2:00 PM, Yonik Seeley wrote: > On Fri, May 15, 2009 at 1:06 PM, Michael McCandless > wrote: >> Otherwise, I only know of one other intermittent failure for >> TestStressIndexing2.testRandomIWReader, which is sometimes it fails to >> close all files it had opened... haven't

Re: Build failed in Hudson: Lucene-trunk #828

2009-05-15 Thread Yonik Seeley
On Fri, May 15, 2009 at 1:06 PM, Michael McCandless wrote: > Otherwise, I only know of one other intermittent failure for > TestStressIndexing2.testRandomIWReader, which is sometimes it fails to > close all files it had opened... haven't gotten to the bottom of that > one yet. Is there a JIRA iss

Re: Build failed in Hudson: Lucene-trunk #828

2009-05-15 Thread Michael McCandless
OK, this failure was in fact caused by LUCENE-1596 (because the test uses a MultiTermDocs/Enum to step through the docs, comparing them across the two readers). But, in digging into this one, I found & fixed a separate thread hazard -- I'll open an issue shortly. Otherwise, I only know of one oth

RE: Build failed in Hudson: Lucene-trunk #828

2009-05-15 Thread Uwe Schindler
This error is in TestStressIndexing2.testRandomIWReader. I checked out locally, the problem is not the reproducible by same random seed (so r.setSeed() to the seed from error log does not reproduce the bug). This test seems to fail very often; maybe there is a real multi-thread synchronization bug.