[
https://issues.apache.org/jira/browse/HBASE-12229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14173440#comment-14173440
]
Hadoop QA commented on HBASE-12229:
-----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12675224/HBASE-12229_master_v1.patch
against trunk revision .
ATTACHMENT ID: 12675224
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 6 new
or modified tests.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{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:
org.apache.hadoop.hbase.client.TestCloneSnapshotFromClientWithRegionReplicas
org.apache.hadoop.hbase.TestZooKeeper
org.apache.hadoop.hbase.client.TestRestoreSnapshotFromClientWithRegionReplicas
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/11372//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11372//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11372//artifact/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11372//artifact/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11372//artifact/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11372//artifact/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11372//artifact/patchprocess/newPatchFindbugsWarningshbase-rest.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11372//artifact/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11372//artifact/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11372//artifact/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11372//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11372//artifact/patchprocess/newPatchFindbugsWarningshbase-annotations.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/11372//console
This message is automatically generated.
> NullPointerException in SnapshotTestingUtils
> --------------------------------------------
>
> Key: HBASE-12229
> URL: https://issues.apache.org/jira/browse/HBASE-12229
> Project: HBase
> Issue Type: Bug
> Components: test
> Affects Versions: 0.98.7
> Reporter: Dima Spivak
> Assignee: Dima Spivak
> Priority: Minor
> Attachments: HBASE-12229.patch, HBASE-12229_master_v1.patch,
> HBASE-12229_v1.patch, HBASE-12229_v2.patch, HBASE-12229_v2.patch
>
>
> I tracked down occasional flakiness in TestRestoreSnapshotFromClient to a
> potential NPE in SnapshotTestingUtils#waitForTableToBeOnline. In short, some
> tests in TestRestoreSnapshot... create a table and then invoke
> SnapshotTestingUtils#waitForTableToBeOnline, but this method assumes that
> regions have been assigned by the time it's invoked (which is not always the
> case).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
