[
https://issues.apache.org/jira/browse/HBASE-14915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15054769#comment-15054769
]
stack commented on HBASE-14915:
-------------------------------
You could do category based timeouts rather, as per HBASE-13127, rather than
add a timeout on each method. Just add the below to the head of the testsuite
class:
@Rule public final TestRule timeout =
CategoryBasedTimeout.builder().withTimeout(this.getClass()).
withLookingForStuckThread(true).build();
... e.g.:
{code}
71 public class TestScanner {
72 @Rule public TestName name = new TestName();
73 @Rule public final TestRule timeout = CategoryBasedTimeout.builder().
74 withTimeout(this.getClass()).withLookingForStuckThread(true).build();
...
{code}
Doing above would have junit timeout a test at 50 seconds which is how long
Medium tests are supposed to run for (in refguide is says how long each
category is expected to run).
You could add this on commit. Your patch looks good. Lets try it. Leave issue
open and if it works, we can close it, else we'll try something else.... Nice
one [~chenheng]
> Hanging test : org.apache.hadoop.hbase.mapreduce.TestImportExport
> -----------------------------------------------------------------
>
> Key: HBASE-14915
> URL: https://issues.apache.org/jira/browse/HBASE-14915
> Project: HBase
> Issue Type: Sub-task
> Components: hangingTests
> Reporter: stack
> Attachments: HBASE-14915-branch-1.2.patch,
> HBASE-14915_v1-branch-1.2.patch, HBASE-14915_v2-branch-1.2.patch,
> HBASE-14915_v2-branch-1.2.patch
>
>
> This test hangs a bunch:
> Here is latest:
> https://builds.apache.org/job/HBase-1.2/418/jdk=latest1.7,label=Hadoop/consoleText
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
