You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2017/10/31 23:20:00 UTC

[jira] [Resolved] (HBASE-19135) TestWeakObjectPool time out

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

stack resolved HBASE-19135.
---------------------------
       Resolution: Fixed
         Assignee: stack
     Hadoop Flags: Reviewed
    Fix Version/s: 2.0.0-beta-1

Pushed to master and branch-2. Thanks for reviews. (Tried to backport to branch-1 but failed apply)

> TestWeakObjectPool time out
> ---------------------------
>
>                 Key: HBASE-19135
>                 URL: https://issues.apache.org/jira/browse/HBASE-19135
>             Project: HBase
>          Issue Type: Bug
>            Reporter: stack
>            Assignee: stack
>             Fix For: 2.0.0-beta-1
>
>         Attachments: HBASE-19135.master.001.patch
>
>
> On last branch-2 build, this small test timed out. Timeout is 1second which given how hostile apache infra has been of late is way to short. Change the test to do category-base timeout.
> Here is the report:
> {code}
> Regression
> org.apache.hadoop.hbase.util.TestWeakObjectPool.testCongestion
> Failing for the past 1 build (Since Failed#778 )
> Took 1.1 sec.
> add description
> Error Message
> test timed out after 1000 milliseconds
> Stacktrace
> org.junit.runners.model.TestTimedOutException: test timed out after 1000 milliseconds
> 	at org.apache.hadoop.hbase.util.TestWeakObjectPool.testCongestion(TestWeakObjectPool.java:128)
> Standard Output
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)