You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Stephen Yuan Jiang (JIRA)" <ji...@apache.org> on 2015/05/21 19:51:17 UTC
[jira] [Created] (HBASE-13741) Disable
TestRegionObserverInterface.testRecovery and testLegacyRecovery
Stephen Yuan Jiang created HBASE-13741:
------------------------------------------
Summary: Disable TestRegionObserverInterface.testRecovery and testLegacyRecovery
Key: HBASE-13741
URL: https://issues.apache.org/jira/browse/HBASE-13741
Project: HBase
Issue Type: Bug
Affects Versions: 1.1.0, 2.0.0, 1.2.0
Reporter: Stephen Yuan Jiang
Assignee: Stephen Yuan Jiang
Priority: Minor
This is related to HBASE-13391.
When testing 1.1 release in Windows environment, both org.apache.hadoop.hbase.coprocessor.TestRegionObserverInterface.testRecovery and org.apache.hadoop.hbase.coprocessor.TestRegionObserverInterface.testLegacyRecovery failed frequently. testLegacyRecovery fails more frequently.
{noformat}
java.lang.AssertionError: Result of org.apache.hadoop.hbase.coprocessor.SimpleRegionObserver.getCtPreWALRestore is expected to be 1, while we get 0
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.assertTrue(Assert.java:41)
at org.apache.hadoop.hbase.coprocessor.TestRegionObserverInterface.verifyMethodResult(TestRegionObserverInterface.java:746)
at org.apache.hadoop.hbase.coprocessor.TestRegionObserverInterface.testRecovery(TestRegionObserverInterface.java:630)
java.lang.AssertionError: Result of org.apache.hadoop.hbase.coprocessor.SimpleRegionObserver$Legacy.getCtPreWALRestore is expected to be 1, while we get 0
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.assertTrue(Assert.java:41)
at org.apache.hadoop.hbase.coprocessor.TestRegionObserverInterface.verifyMethodResult(TestRegionObserverInterface.java:746)
at org.apache.hadoop.hbase.coprocessor.TestRegionObserverInterface.testLegacyRecovery(TestRegionObserverInterface.java:680)
{noformat}
Base on [~apurtell], "we're not waiting for recovery to complete, just hoping we race behind it so the test passes. These test cases need a redo (or a rip out)" - the HBASE-13391 tracks the real fix; this JIRA (based on suggestion of [~busbey]) disable these two tests so that we will not run into false alarm frequently.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)