[
https://issues.apache.org/jira/browse/HBASE-5793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13254246#comment-13254246
]
Hadoop QA commented on HBASE-5793:
----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12522685/hbase-5793.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 3 new or modified tests.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
-1 findbugs. The patch appears to introduce 3 new Findbugs (version 1.3.9)
warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
-1 core tests. The patch failed these unit tests:
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/1530//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/1530//artifact/trunk/patchprocess/newPatchFindbugsWarnings.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/1530//console
This message is automatically generated.
> TestHBaseFsck#TestNoHdfsTable test hangs after HBASE-5747
> ---------------------------------------------------------
>
> Key: HBASE-5793
> URL: https://issues.apache.org/jira/browse/HBASE-5793
> Project: HBase
> Issue Type: Sub-task
> Affects Versions: 0.96.0
> Reporter: Jonathan Hsieh
> Assignee: Jonathan Hsieh
> Attachments: hbase-5793.patch
>
>
> After the HBASE-5747 modification, this one particular case hangs.
> {code}
> mvn test -PlocalTests -Dtest=TestHBaseFsck
> {code}
> It was hanging on a scan of a table that the test deleted. It expected a call
> to thrown an exception after a timeout. HBASE-5747 changed the timeout to a
> larger number of retries which caused mvn to fail the test.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
