8:29 AM
To: java-dev@lucene.apache.org
Subject: RE: Build failed in Hudson: Lucene-trunk #1034
When looking around, TestStressIndexing has the same problem (only the
time
is there 1.0 sec). Attached is a patch also for that. Also this test does
not use a volatile variable for the error
See http://hudson.zones.apache.org/hudson/job/Lucene-trunk/1034/changes
Changes:
[uschindler] LUCENE-1769: disable clover reports on assert statements
[uschindler] LUCENE-1769: Add also the opposite assert statement
[uschindler] LUCENE-1769: Improve clover analysis and separate core / bw
To: java-dev@lucene.apache.org
Subject: Build failed in Hudson: Lucene-trunk #1034
See http://hudson.zones.apache.org/hudson/job/Lucene-trunk/1034/changes
Changes:
[uschindler] LUCENE-1769: disable clover reports on assert statements
[uschindler] LUCENE-1769: Add also the opposite
A new strange test failure:
[junit] Testcase:
testDuringAddDelete(org.apache.lucene.index.TestIndexWriterReader):
FAILED
[junit] null
[junit] junit.framework.AssertionFailedError: null
[junit] at
org.apache.lucene.index.TestIndexWriterReader.testDuringAddDelete(TestInde
, December 18, 2009 7:56 AM
To: java-dev@lucene.apache.org
Subject: RE: Build failed in Hudson: Lucene-trunk #1034
A new strange test failure:
[junit] Testcase:
testDuringAddDelete(org.apache.lucene.index.TestIndexWriterReader):
FAILED
[junit] null
[junit
@lucene.apache.org
Subject: RE: Build failed in Hudson: Lucene-trunk #1034
Here the patch, Mike, does this look ok?
When committed we can start a new Hudson run, if you like :-)
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
