On 09/16/2008 at 6:17 AM, Michael McCandless wrote:
> I'm also unable to get the test to fail after stress testing it,
> though I did hit OOM errors before giving the JRE enough RAM.
>
> Is it possible your machine was memory starved at the time?
Possible, yes: the machine has 2GB of RAM, and I h
Argh it's is a Heisenbug!
I'll keep running the test over & over to see if I can get it to happen.
And I'll at least commit that change so when it does happen again we
get more detail.
Mike
Steven A Rowe wrote:
I applied the patch and then the test refused to fail.
I removed the patch a
I applied the patch and then the test refused to fail.
I removed the patch and the test still refused to fail.
I'm not sure what happened - AFAIK I didn't change anything. I ran the test
about five times previously and it always failed :(.
Maybe it's Microsoft's gentle way of telling me it's t
I can't get it to fail, on Windows Server 2003, Sun Java 1.4.2_15.
Unfortunately the test doesn't give us the traceback on failure (just
the message "null"). Can you apply this, get the test to fail, and
post back the traceback?
Index: src/test/org/apache/lucene/index/TestIndexReaderReope
When I try to run all of the unit tests, TestIndexReaderReopen is consistently
failing:
[junit] Testsuite: org.apache.lucene.index.TestIndexReaderReopen
[junit] null)
[junit] Tests run: 13, Failures: 1, Errors: 0, Time elapsed: 116.375 sec
[junit]
[junit] Testcase:
testThrea
