On Thu, Mar 19, 2015 at 1:38 PM, Dawid Weiss <dawid.we...@cs.put.poznan.pl> wrote:
> There is no extra "heartbeat" emitted form the forked process back to > the parent, but there could be. If a stalled process emitted a thread > dump on every heartbeat this would look scary though (especially for > slower machines/ tests), wouldn't it? I agree: this would be too much. > It's this issue, Mike: > https://github.com/carrotsearch/randomizedtesting/issues/132 Thanks. > I'd love to say I can look at fixing it soon, but I have plenty of > things on the backlog right now. I promise to return to it eventually. > Sorry! OK! > Also, this does *not* have to be implemented in the runner itself... > it can be a JUnit test rule that would spawn its own watchdog and, if > the test doesn't return in the given deadline, takes periodic stack > trace probes, emitting them to regular sysout. You wouldn't get these > dumps immediately (because sysout is suppressed from console, > normally), but eventually if a test times out all of the sysouts would > be printed. This would maybe be a good solution... I wouldn't want to see the thread stacks until the test finally timed out at which point I'd like to see N of them. It would spawn a new thread for each test case right? And it'd have to stop that thread when the test completes (success or failure)... Mike McCandless http://blog.mikemccandless.com --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
