[
https://issues.apache.org/jira/browse/HBASE-12410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14194242#comment-14194242
]
Dima Spivak commented on HBASE-12410:
-------------------------------------
Haha, best description ever, [~stack].
To find hanging tests from Jenkins output, use [~manukranthk]'s iteration of
the findHangingTests tool in ./dev-support. Just pass the Jenkins URL of the
console output (ending in either consoleFull or consoleText) of the job and it
will print jobs that started running without finishing. For example:
{code}
dspivak-mbp:dev-support dspivak$ ./findHangingTests.py
https://builds.apache.org/job/HBase-1.0/400/consoleText
Fetching the console output from the URL
Printing hanging tests
Hanging test : org.apache.hadoop.hbase.client.TestAdmin
Printing Failing tests
{code}
> Zombie hunting tips!
> --------------------
>
> Key: HBASE-12410
> URL: https://issues.apache.org/jira/browse/HBASE-12410
> Project: HBase
> Issue Type: Brainstorming
> Reporter: stack
>
> Here are some tips from Mr Charlton Heston (@dima spivak) and World War Z
> Brad Pitt ([~apurtell]), famous Zombie killers, on how to figure why tests
> are hanging:
> bq. Set -Dsurefire.timeout=0 to the mvn command which sets the process
> timeout to unlimited.
> Above is good for figuring what is sticking around.
> bq. When hunting zombies locally you can also set the first part and second
> part fork modes to "always" so each test runs in its own VM, then loop the
> unit test suite, watch for stragglers, then jstack. Works well because you
> can be sure every stack in the dump is relevant for the hung test.
> Lets keep this issue open and add tips for tests for nailing those that won't
> die.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
