[
https://issues.apache.org/jira/browse/HBASE-7142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13496084#comment-13496084
]
Hudson commented on HBASE-7142:
-------------------------------
Integrated in HBase-0.94-security #83 (See
[https://builds.apache.org/job/HBase-0.94-security/83/])
HBASE-7142 TestSplitLogManager#testDeadWorker may fail because of hard
limit on the TimeoutMonitor's timeout period (Himanshu) (Revision 1408119)
Result = SUCCESS
larsh :
Files :
*
/hbase/branches/0.94/src/test/java/org/apache/hadoop/hbase/master/TestSplitLogManager.java
> TestSplitLogManager#testDeadWorker may fail because of hard limit on the
> TimeoutMonitor's timeout period
> --------------------------------------------------------------------------------------------------------
>
> Key: HBASE-7142
> URL: https://issues.apache.org/jira/browse/HBASE-7142
> Project: HBase
> Issue Type: Test
> Components: test
> Affects Versions: 0.94.2
> Reporter: Himanshu Vashishtha
> Assignee: Himanshu Vashishtha
> Priority: Minor
> Fix For: 0.94.3
>
> Attachments: HBASE-7142.patch
>
>
> The timeout in testDeadWorker is set to 1 sec, it is the same as the
> TimeoutMonitor thread timeout. In some case, this may fail:
> {code}
> java.lang.AssertionError
> at org.junit.Assert.fail(Assert.java:92)
> at org.junit.Assert.assertTrue(Assert.java:43)
> at org.junit.Assert.assertTrue(Assert.java:54)
> at
> org.apache.hadoop.hbase.master.TestSplitLogManager.waitForCounter(TestSplitLogManager.java:147)
> at
> org.apache.hadoop.hbase.master.TestSplitLogManager.waitForCounter(TestSplitLogManager.java:127)
> at
> org.apache.hadoop.hbase.master.TestSplitLogManager.testDeadWorker(TestSplitLogManager.java:433)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> {code}
> Fix is to increase the timeout for this test. Its not needed in trunk as the
> timeout is 3 seconds.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
