[
https://issues.apache.org/jira/browse/HBASE-5223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13188188#comment-13188188
]
Hadoop QA commented on HBASE-5223:
----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12510923/5223.txt
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 -145 warning
messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
-1 findbugs. The patch appears to introduce 82 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.replication.TestReplication
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/799//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/799//artifact/trunk/patchprocess/newPatchFindbugsWarnings.html
Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/799//console
This message is automatically generated.
> TestMetaReaderEditor is missing call to CatalogTracker.stop()
> -------------------------------------------------------------
>
> Key: HBASE-5223
> URL: https://issues.apache.org/jira/browse/HBASE-5223
> Project: HBase
> Issue Type: Test
> Reporter: Zhihong Yu
> Fix For: 0.94.0, 0.92.1
>
> Attachments: 5223.txt
>
>
> I noticed that TestMetaReaderEditor hung on 0.92 Jenkins builds - see
> https://builds.apache.org/view/G-L/view/HBase/job/HBase-0.92/249/console
> It turns out that CatalogTracker.stop() is missing.
--
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
