[
https://issues.apache.org/jira/browse/HBASE-6022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13278268#comment-13278268
]
Hadoop QA commented on HBASE-6022:
----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12527906/HBASE-6022-0.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified
tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
+1 hadoop23. The patch compiles against the hadoop 0.23.x profile.
+1 javadoc. The javadoc tool did not generate any warning messages.
-1 javac. The applied patch generated 13 javac compiler warnings (more
than the trunk's current 5 warnings).
-1 findbugs. The patch appears to introduce 32 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 passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/1916//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/1916//artifact/trunk/patchprocess/newPatchFindbugsWarnings.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/1916//console
This message is automatically generated.
> Include Junit in the libs when packaging so that TestAcidGaurntee can run
> -------------------------------------------------------------------------
>
> Key: HBASE-6022
> URL: https://issues.apache.org/jira/browse/HBASE-6022
> Project: HBase
> Issue Type: Improvement
> Reporter: Elliott Clark
> Assignee: Elliott Clark
> Fix For: 0.94.1
>
> Attachments: HBASE-6022-0.patch
>
>
> If JUnit is not in the libs folder running the test acid command fails.
--
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
