[
https://issues.apache.org/jira/browse/HBASE-4480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13142855#comment-13142855
]
Hadoop QA commented on HBASE-4480:
----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12502093/HBASE-4480_v4.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 2 new or modified tests.
-1 javadoc. The javadoc tool appears to have generated -164 warning
messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
-1 findbugs. The patch appears to introduce 46 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.master.TestDistributedLogSplitting
org.apache.hadoop.hbase.master.TestMasterFailover
org.apache.hadoop.hbase.mapreduce.TestHFileOutputFormat
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/149//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/149//artifact/trunk/patchprocess/newPatchFindbugsWarnings.html
Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/149//console
This message is automatically generated.
> Testing script to simplify local testing
> ----------------------------------------
>
> Key: HBASE-4480
> URL: https://issues.apache.org/jira/browse/HBASE-4480
> Project: HBase
> Issue Type: Improvement
> Affects Versions: 0.90.4
> Reporter: Jesse Yates
> Priority: Minor
> Labels: test
> Fix For: 0.94.0
>
> Attachments: HBASE-4480.patch, HBASE-4480_v2.patch,
> HBASE-4480_v3.patch, HBASE-4480_v4.patch, runtest-no-npe-check.sh,
> runtest.sh, runtest2.sh
>
>
> As mentioned by http://search-hadoop.com/m/r2Ab624ES3e and
> http://search-hadoop.com/m/cZjDH1ykGIA it would be nice if we could have a
> script that would handle more of the finer points of running/checking our
> test suite.
> This script should:
> (1) Allow people to determine which tests are hanging/taking a long time to
> run
> (2) Allow rerunning of particular tests to make sure it wasn't an artifact of
> running the whole suite that caused the failure
> (3) Allow people to specify to run just unit tests or also integration tests
> (essentially wrapping calls to 'maven test' and 'maven verify').
> This script should just be a convenience script - running tests directly from
> maven should not be impacted.
--
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
