Details
Description
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.
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)
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.
Attachments
Attachments
Issue Links
- is related to
-
HBASE-13391 TestRegionObserverInterface frequently failing on branch-1
- Closed