[ https://issues.apache.org/jira/browse/YARN-571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13665857#comment-13665857 ]
Hadoop QA commented on YARN-571: -------------------------------- {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12584601/YARN-571.20130522.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 28 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:red}-1 core tests{color}. The patch failed these unit tests in hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-distributedshell hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-tests: org.apache.hadoop.yarn.server.TestContainerManagerSecurity {color:green}+1 contrib tests{color}. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-YARN-Build/998//testReport/ Console output: https://builds.apache.org/job/PreCommit-YARN-Build/998//console This message is automatically generated. > User should not be part of ContainerLaunchContext > ------------------------------------------------- > > Key: YARN-571 > URL: https://issues.apache.org/jira/browse/YARN-571 > Project: Hadoop YARN > Issue Type: Sub-task > Reporter: Hitesh Shah > Assignee: Omkar Vinit Joshi > Attachments: YARN-571-20130415.2.txt, YARN-571-20130418.txt, > YARN-571.20130522.1.patch, YARN-571.20130522.patch > > > Today, a user is expected to set the user name in the CLC when either > submitting an application or launching a container from the AM. This does not > make sense as the user can/has been identified by the RM as part of the RPC > layer. > Solution would be to move the user information into either the Container > object or directly into the ContainerToken which can then be used by the NM > to launch the container. This user information would set into the container > by the RM. -- 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