[
https://issues.apache.org/jira/browse/HADOOP-6332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12865388#action_12865388
]
Hadoop QA commented on HADOOP-6332:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12444028/HADOOP-6332.0.22.patch
against trunk revision 941662.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 52 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 does not introduce any new Findbugs warnings.
-1 release audit. The applied patch generated 2 release audit warnings
(more than the trunk's current 1 warnings).
+1 core tests. The patch passed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/512/testReport/
Release audit warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/512/artifact/trunk/patchprocess/releaseAuditDiffWarnings.txt
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/512/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/512/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/512/console
This message is automatically generated.
> Large-scale Automated Test Framework
> ------------------------------------
>
> Key: HADOOP-6332
> URL: https://issues.apache.org/jira/browse/HADOOP-6332
> Project: Hadoop Common
> Issue Type: New Feature
> Components: test
> Affects Versions: 0.22.0
> Reporter: Arun C Murthy
> Assignee: Konstantin Boudnik
> Fix For: 0.22.0
>
> Attachments: 6332-phase2.fix1.patch, 6332-phase2.fix2.patch,
> 6332-phase2.patch, 6332.patch, 6332.patch, 6332.patch, 6332_v1.patch,
> 6332_v2.patch, HADOOP-6332-MR.patch, HADOOP-6332-MR.patch,
> HADOOP-6332.0.22.patch, HADOOP-6332.0.22.patch, HADOOP-6332.0.22.patch,
> HADOOP-6332.0.22.patch, HADOOP-6332.0.22.patch, HADOOP-6332.patch,
> HADOOP-6332.patch
>
>
> Hadoop would benefit from having a large-scale, automated, test-framework.
> This jira is meant to be a master-jira to track relevant work.
> ----
> The proposal is a junit-based, large-scale test framework which would run
> against _real_ clusters.
> There are several pieces we need to achieve this goal:
> # A set of utilities we can use in junit-based tests to work with real,
> large-scale hadoop clusters. E.g. utilities to bring up to deploy, start &
> stop clusters, bring down tasktrackers, datanodes, entire racks of both etc.
> # Enhanced control-ability and inspect-ability of the various components in
> the system e.g. daemons such as namenode, jobtracker should expose their
> data-structures for query/manipulation etc. Tests would be much more relevant
> if we could for e.g. query for specific states of the jobtracker, scheduler
> etc. Clearly these apis should _not_ be part of the production clusters -
> hence the proposal is to use aspectj to weave these new apis to
> debug-deployments.
> ----
> Related note: we should break up our tests into at least 3 categories:
> # src/test/unit -> Real unit tests using mock objects (e.g. HDFS-669 &
> MAPREDUCE-1050).
> # src/test/integration -> Current junit tests with Mini* clusters etc.
> # src/test/system -> HADOOP-6332 and it's children
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
