[
https://issues.apache.org/jira/browse/HBASE-5887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13263276#comment-13263276
]
Hadoop QA commented on HBASE-5887:
----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12524789/hbase-5887.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 2 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/1661//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/1661//artifact/trunk/patchprocess/newPatchFindbugsWarnings.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/1661//console
This message is automatically generated.
> Make TestAcidGuarantees usable for system testing.
> --------------------------------------------------
>
> Key: HBASE-5887
> URL: https://issues.apache.org/jira/browse/HBASE-5887
> Project: HBase
> Issue Type: Improvement
> Affects Versions: 0.92.0, 0.92.1, 0.94.0
> Reporter: Jonathan Hsieh
> Assignee: Jonathan Hsieh
> Attachments: hbase-5887-92.patch, hbase-5887.patch
>
>
> Currently, the TestAcidGuarantees run via main() will always abort with an
> NPE because it digs into a non-existant HBaseTestingUtility for a flusher
> thread. We should tool this up so that it works properly from the command
> line. This would be a very useful long running test when used in conjunction
> with fault injections to verify row acid properties.
--
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
