On Tue, Aug 14, 2012 at 3:36 PM, Dawid Weiss <dawid.we...@cs.put.poznan.pl> wrote: > If you do ignore even one suite and it leaves threads behind then:
I'm only trying to run/loop a single test to reproduce a different problem. > 1) it defeats the purpose of having those checks (and I really think > having background threads that do something after a suite completes is > a Bad Thing (tm)). > > 2) it would hurt my feelings, really. I've put a lot of time and > effort in this not to make it an annoyance but to make it a helpful > tool to make tests better (and repeatable). Whether or not it does the > job is a longer discussion of course. > > Can you at least point at which test case causes the problem? What > threads are leaking (and why they cannot be cleanly shut down)? Some of the chaos* tests that are currently ignored (that I am un-ignoring locally to work on). The issue is not whether thread leaks from tests are bad or not, it's a matter of priority. > Finally, the answer if you really insist. > > 1) either annotate your suite class with @ThreadLeakScope(Scope.NONE) Thanks! -Yonik http://lucidworks.com --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
