[
https://issues.apache.org/jira/browse/HBASE-13617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14527811#comment-14527811
]
Hudson commented on HBASE-13617:
--------------------------------
FAILURE: Integrated in HBase-1.1 #465 (See
[https://builds.apache.org/job/HBase-1.1/465/])
HBASE-13617 TestReplicaWithCluster.testChangeTable timeout (Stephen Yuan Jiang)
(stack: rev c552e37b41f52bbcdef431ee71cdbaa3f4d5edbc)
*
hbase-server/src/test/java/org/apache/hadoop/hbase/client/TestReplicaWithCluster.java
> TestReplicaWithCluster.testChangeTable timeout
> ----------------------------------------------
>
> Key: HBASE-13617
> URL: https://issues.apache.org/jira/browse/HBASE-13617
> Project: HBase
> Issue Type: Bug
> Affects Versions: 2.0.0, 1.1.0, 1.2.0
> Reporter: Stephen Yuan Jiang
> Assignee: Stephen Yuan Jiang
> Fix For: 2.0.0, 1.1.0, 1.2.0
>
> Attachments: HBASE-13617.patch
>
>
> In our internal test TestReplicaWithCluster.testChangeTable got a timeout.
> HBASE-12170 bumped TestReplicaWithCluster.testReplicaAndReplication timeout
> from 2 minutes to 5 minutes, but leaves other tests in the same package
> unchanged.
> When I run the test in my fast Mac, the run time of
> TestReplicaWithCluster.testChangeTable (~16 seconds) is about half of
> TestReplicaWithCluster.testReplicaAndReplication (~31 seconds).
> We should increase the timeout in TestReplicaWithCluster.testChangeTable to
> avoid test failure in slow environment.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
