[
https://issues.apache.org/jira/browse/HBASE-22488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16850580#comment-16850580
]
Guanghao Zhang commented on HBASE-22488:
----------------------------------------
Pushed to branch-2.1, too.
> Cleanup the explicit timeout value for test methods
> ---------------------------------------------------
>
> Key: HBASE-22488
> URL: https://issues.apache.org/jira/browse/HBASE-22488
> Project: HBase
> Issue Type: Improvement
> Reporter: Guanghao Zhang
> Assignee: Guanghao Zhang
> Priority: Major
> Fix For: 3.0.0, 2.2.0, 2.3.0
>
>
> After HBASE-19948, no need to add explicit timeout for test methods. But
> there are some new test methods which used explicit timeout and easy to fail
> when precommit job run them. One example is
> [https://builds.apache.org/job/PreCommit-HBASE-Build/436/testReport/org.apache.hadoop.hbase.coprocessor/TestMetaTableMetrics/testConcurrentAccess/]
>
> See [http://hbase.apache.org/book.html#hbase.unittests.timeouts]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
