You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Samir Ahmic (JIRA)" <ji...@apache.org> on 2015/10/29 14:31:27 UTC

[jira] [Updated] (HBASE-14718) Increase sleep time in TestRegionMover#testLoadWithoutAck

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

Samir Ahmic updated HBASE-14718:
--------------------------------
    Priority: Minor  (was: Major)

> Increase sleep time in TestRegionMover#testLoadWithoutAck
> ---------------------------------------------------------
>
>                 Key: HBASE-14718
>                 URL: https://issues.apache.org/jira/browse/HBASE-14718
>             Project: HBase
>          Issue Type: Test
>          Components: test
>    Affects Versions: 2.0.0
>            Reporter: Samir Ahmic
>            Assignee: Samir Ahmic
>            Priority: Minor
>
> I have notice this failed while working on [HBASE-14664| https://issues.apache.org/jira/browse/HBASE-14664]. Looks like test outcome depends on how fast is machine running this test. On my laptom threshold is 50ms when test start to fail. I assume on Apache Jenkins 100ms is very close to treshold based on exception:
> {code}
> java.lang.AssertionError: expected:<3> but was:<2>
> 	at org.junit.Assert.fail(Assert.java:88)
> 	at org.junit.Assert.failNotEquals(Assert.java:834)
> 	at org.junit.Assert.assertEquals(Assert.java:645)
> 	at org.junit.Assert.assertEquals(Assert.java:631)
> 	at org.apache.hadoop.hbase.util.TestRegionMover.testLoadWithoutAck(TestRegionMover.java:110)
> {code} 
> So my suggestion is to increase this to 150ms.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)