[
https://issues.apache.org/jira/browse/HBASE-5420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13209959#comment-13209959
]
Hadoop QA commented on HBASE-5420:
----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12514915/HBASE-5420-v1.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 appears to have generated -136 warning
messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
-1 findbugs. The patch appears to introduce 157 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:
org.apache.hadoop.hbase.mapreduce.TestHFileOutputFormat
org.apache.hadoop.hbase.mapred.TestTableMapReduce
org.apache.hadoop.hbase.mapreduce.TestImportTsv
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/978//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/978//artifact/trunk/patchprocess/newPatchFindbugsWarnings.html
Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/978//console
This message is automatically generated.
> TestImportTsv does not shut down MR Cluster correctly (fails against 0.23
> hadoop)
> ---------------------------------------------------------------------------------
>
> Key: HBASE-5420
> URL: https://issues.apache.org/jira/browse/HBASE-5420
> Project: HBase
> Issue Type: Bug
> Components: test
> Affects Versions: 0.94.0, 0.92.0
> Reporter: Gregory Chanan
> Assignee: Gregory Chanan
> Attachments: HBASE-5420-v1.patch, HBASE-5420.patch
>
>
> Test calls startMiniMapReduceCluster() but never calls
> shutdownMiniMapReduceCluster().
> This causes failures with -Dhadoop.profile=23 when both testMROnTable and
> testMROnTableWithCustomMapper are run, because the cluster cannot start up
> properly for the second 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
