[
https://issues.apache.org/jira/browse/HADOOP-9512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13647218#comment-13647218
]
Hadoop QA commented on HADOOP-9512:
-----------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12581463/HADOOP-9512.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 5 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-tools/hadoop-tools-dist hadoop-tools/hadoop-vaidya.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/2506//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/2506//console
This message is automatically generated.
> Add Hadoop-Vaidya to branch2
> ----------------------------
>
> Key: HADOOP-9512
> URL: https://issues.apache.org/jira/browse/HADOOP-9512
> Project: Hadoop Common
> Issue Type: New Feature
> Components: tools
> Affects Versions: 2.0.4-alpha
> Reporter: nemon lou
> Attachments: HADOOP-9512.patch, HADOOP-9512.patch, HADOOP-9512.patch
>
>
> Hadoop-Vaidya exists in hadoop1.0 series and we need to add it to hadoop
> branch2.
> The only changes for supporting Hadoop2 are job history perser and job
> counters ,etc.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
