You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Guanghao Zhang (JIRA)" <ji...@apache.org> on 2019/05/29 07:14:00 UTC

[jira] [Resolved] (HBASE-22488) Cleanup the explicit timeout value for test methods

     [ https://issues.apache.org/jira/browse/HBASE-22488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Guanghao Zhang resolved HBASE-22488.
------------------------------------
       Resolution: Fixed
    Fix Version/s: 2.3.0
                   2.2.0
                   3.0.0

Pushed to branch-2.2+. Thanks [~Apache9] for reviewing.

> 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)