[ https://issues.apache.org/jira/browse/HADOOP-10029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13791967#comment-13791967 ]
Hadoop QA commented on HADOOP-10029: ------------------------------------ {color:green}+1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12607875/HADOOP-10029.5.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}. 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-common-project/hadoop-common. {color:green}+1 contrib tests{color}. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HADOOP-Build/3201//testReport/ Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/3201//console This message is automatically generated. > Specifying har file to MR job fails in secure cluster > ----------------------------------------------------- > > Key: HADOOP-10029 > URL: https://issues.apache.org/jira/browse/HADOOP-10029 > Project: Hadoop Common > Issue Type: Bug > Components: fs > Affects Versions: 2.0.0-alpha > Reporter: Suresh Srinivas > Assignee: Suresh Srinivas > Attachments: HADOOP-10029.1.patch, HADOOP-10029.2.patch, > HADOOP-10029.3.patch, HADOOP-10029.4.patch, HADOOP-10029.4.patch, > HADOOP-10029.5.patch, HADOOP-10029.6.patch, HADOOP-10029.patch > > > This is an issue found by [~rramya]. See the exception stack trace in the > following comment. -- This message was sent by Atlassian JIRA (v6.1#6144)