> How hard/reasonable would it be to see a full thread dump on every > heartbeat of a slow running test when the test finally times out?
The "heartbeat" message is not actually originating from the forked process, it is merely an information issued by the test runner to let you know that the forked process: 1) hasn't died, 2) the forked runner's main method has not completed. 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? It's this issue, Mike: https://github.com/carrotsearch/randomizedtesting/issues/132 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! 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. Dawid --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org