> It said: --tests
> "org.apache.lucene.index.TestDocumentsWriterStallControl.classMethod"
> But it should be: --tests
> "org.apache.lucene.index.TestDocumentsWriterStallControl.testAcquireReleaseRace"
> ?
> Or maybe no test method at all since we don't know who is truly to blame?
>
The reasons are more cleanly stated in the exception that is printed on the
console (not in the summary):
org.apache.lucene.index.TestDocumentsWriterStallControl >
testAcquireReleaseRace FAILED
java.lang.Exception: Test abandoned because suite timeout was reached.
at __randomizedtesting.SeedInfo.seed([C412FA486B53A28D]:0)
org.apache.lucene.index.TestDocumentsWriterStallControl > classMethod FAILED
java.lang.Exception: Suite timeout exceeded (>= 7200000 msec).
at __randomizedtesting.SeedInfo.seed([C412FA486B53A28D]:0)
The first exception happened in the test (and it's a faux exception
substituted by the runner when the suite timed out); the second is thrown
from class-level (rule).
I agree the message could be improved but these corner cases (timeouts
outside of the normal test code control flow) are hard because they're not
anticipated by the regular junit architecture.
This aside, I think we should include gradle tasks that download those test
data sets. It'd make life easier.
D.
