If you do ignore even one suite and it leaves threads behind then: 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)? Finally, the answer if you really insist. 1) either annotate your suite class with @ThreadLeakScope(Scope.NONE) or 2) if these threads are really something that cannot be cleanly shut down and you're certain they have no side effects, add them to a filter -- there are certain filters defined already, look up SolrIgnoredThreadsFilter. Dawid On Tue, Aug 14, 2012 at 9:24 PM, Yonik Seeley <yo...@lucidworks.com> wrote: > I'm trying to debug other issues, but I can't seem to get past the new > thread leak checks that cause the test case to fail. > Is there a way to disable these checks? > > -Yonik > http://lucidworks.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: dev-h...@lucene.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
