> 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. > Some of the chaos* tests that are currently ignored (that I am > un-ignoring locally to work on). Yeah, I spent some time on these but they were too complex for me to fix (and I didn't know squat about zookeeper which didn't help). >> 1) either annotate your suite class with @ThreadLeakScope(Scope.NONE) > > Thanks! No problem, ask if you need anything; I understand it's a blackbox and I'll try to help. Dawid --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
