[
https://issues.apache.org/jira/browse/MAPREDUCE-6021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14082540#comment-14082540
]
Hadoop QA commented on MAPREDUCE-6021:
--------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12659163/MAPREDUCE-6021.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 1 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}. There were no new javadoc 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 2.0.3) 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-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/4783//testReport/
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/4783//console
This message is automatically generated.
> MR AM should have working directory in LD_LIBRARY_PATH
> ------------------------------------------------------
>
> Key: MAPREDUCE-6021
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6021
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mr-am
> Affects Versions: 2.4.1
> Reporter: Jason Lowe
> Assignee: Jason Lowe
> Attachments: MAPREDUCE-6021-v2.patch, MAPREDUCE-6021.patch
>
>
> Tasks implicitly pick up shared libraries added to the job because the task
> launch context explicitly adds the container working directory to
> LD_LIBRARY_PATH. However the same is not done for the AM container which is
> inconsistent. User code can run in the AM via output committer, speculator,
> uber job, etc., so the AM's LD_LIBRARY_PATH should have the container work
> directory for consistency with tasks.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
