hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-13741) Disable TestRegionObserverInterface#testRecovery and testLegacyRecovery
Date Fri, 22 May 2015 00:34:18 GMT

    [ https://issues.apache.org/jira/browse/HBASE-13741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14555358#comment-14555358
] 

Hudson commented on HBASE-13741:
--------------------------------

SUCCESS: Integrated in HBase-TRUNK #6507 (See [https://builds.apache.org/job/HBase-TRUNK/6507/])
HBASE-13741 Disable TestRegionObserverInterface#testRecovery and testLegacyRecovery (Stephen
Jiang) (tedyu: rev a9cf353c7581565394eaf2e96c9f99bd829c98d8)
* hbase-server/src/test/java/org/apache/hadoop/hbase/coprocessor/TestRegionObserverInterface.java


> Disable TestRegionObserverInterface#testRecovery and testLegacyRecovery
> -----------------------------------------------------------------------
>
>                 Key: HBASE-13741
>                 URL: https://issues.apache.org/jira/browse/HBASE-13741
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 2.0.0, 1.1.0, 1.2.0
>            Reporter: Stephen Yuan Jiang
>            Assignee: Stephen Yuan Jiang
>            Priority: Minor
>              Labels: Test
>             Fix For: 2.0.0, 1.2.0, 1.1.1
>
>         Attachments: HBASE-13741.v1.patch
>
>
> 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)

Mime
View raw message