On Fri, Jan 27, 2012 at 10:22 AM, Yonik Seeley
<[email protected]> wrote:
>
> FWIW, these aren't real failures of these particular tests, but
> another test bleeding over into these
> caused by a still-running thread later closing a searcher (and it
> get's counted during whatever test is running at the time).
>
Hmm, we had this confusion before and thats why we track resource
leaks from tests that still leave threads running
after all afterClass() methods have finished. In lucene we actually
check this on a per-method basis (after tearDown):
because its annoying for a thread to confusingly cause a different
method even in the same test class to fail.
That's why its important for tests to not leave a lot of threads
running (there are a lot of warnings in solr tests about this):
[junit] ------------- Standard Error -----------------
[junit] WARNING: test class left thread running:
Thread[facetExectutor-4-thread-1,5,main]
[junit] WARNING: test class left thread running:
Thread[facetExectutor-4-thread-2,5,main]
[junit] WARNING: test class left thread running:
Thread[facetExectutor-4-thread-3,5,main]
[junit] WARNING: test class left thread running:
Thread[facetExectutor-4-thread-4,5,main]
[junit] RESOURCE LEAK: test class left 4 thread(s) running
--
lucidimagination.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
