[
https://issues.apache.org/jira/browse/HBASE-13741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14555146#comment-14555146
]
Hadoop QA commented on HBASE-13741:
-----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12734619/HBASE-13741.v1.patch
against master branch at commit e1e8434340f02907976f20566c3e55d8d627d4c4.
ATTACHMENT ID: 12734619
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 3 new
or modified tests.
{color:green}+1 hadoop versions{color}. The patch compiles with all
supported hadoop versions (2.4.1 2.5.2 2.6.0)
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 protoc{color}. The applied patch does not increase the
total number of protoc compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 checkstyle{color}. The applied patch does not increase the
total number of checkstyle errors
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn site goal succeeds with this patch.
{color:red}-1 core tests{color}. The patch failed these unit tests:
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/14151//testReport/
Release Findbugs (version 2.0.3) warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/14151//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors:
https://builds.apache.org/job/PreCommit-HBASE-Build/14151//artifact/patchprocess/checkstyle-aggregate.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/14151//console
This message is automatically generated.
> 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)
