[
https://issues.apache.org/jira/browse/MAPREDUCE-4649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13461518#comment-13461518
]
Hadoop QA commented on MAPREDUCE-4649:
--------------------------------------
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12546225/MAPREDUCE-4649-20120923.txt
against trunk revision .
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 1 new or modified test
files.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 eclipse:eclipse. The patch built with eclipse:eclipse.
+1 findbugs. The patch does not introduce any 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
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-hs.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2870//testReport/
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2870//console
This message is automatically generated.
> mr-jobhistory-daemon.sh needs to be updated post YARN-1
> -------------------------------------------------------
>
> Key: MAPREDUCE-4649
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4649
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: jobhistoryserver
> Affects Versions: 0.23.3, 2.0.2-alpha
> Reporter: Vinod Kumar Vavilapalli
> Assignee: Vinod Kumar Vavilapalli
> Attachments: MAPREDUCE-4649-20120911.txt,
> MAPREDUCE-4649-20120912.txt, MAPREDUCE-4649-20120923.txt
>
>
> Even today, JHS is assuming that YARN_HOME will be same as HADOOP_MAPRED_HOME
> besides other such assumptions. We need to fix it.
--
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
