On Tue, Aug 14, 2012 at 4:08 PM, Dawid Weiss <dawid.we...@cs.put.poznan.pl> wrote: >> I'm only trying to run/loop a single test to reproduce a different problem. > > That's weird... I mean -- thread leaks are checked after a full suite > completes so a loop inside a test shouldn't matter (?). Anyway, you > can also try with -Dtests.iters unless you're really running gazillion > iterations (or want the hooks to run once and the logic multiple times > in which case a loop is a better idea). It should work fine, the > sysouts were a major memory hog, now it's just event objects and > they're much lighter.
Yeah, I had a shell script looping "ant test" because of past issues with tests.iters, but I haven't tried it lately... And if there *is* an issue with a thread from one run messing up another run, best to just do separate "ant test" invocations for now I guess. -Yonik http://lucidworks.com --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
