[
https://issues.apache.org/jira/browse/MAPREDUCE-4612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13446338#comment-13446338
]
Hadoop QA commented on MAPREDUCE-4612:
--------------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12543332/MAPREDUCE-4612.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified
tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
+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-app.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2805//testReport/
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2805//console
This message is automatically generated.
> job summary file permissions not set when its created
> -----------------------------------------------------
>
> Key: MAPREDUCE-4612
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4612
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Affects Versions: 0.23.3, 3.0.0, 2.2.0-alpha
> Reporter: Thomas Graves
> Assignee: Thomas Graves
> Priority: Critical
> Fix For: 0.23.3, 3.0.0, 2.2.0-alpha
>
> Attachments: MAPREDUCE-4612.patch
>
>
> The job summary file permissions are not set when its written out by to the
> done intermediate directory. The conf and jhist files are both set properly
> but the summary file doesn't follow the same path.
> This can cause the summary file to not be copied to the done directory if the
> default umask is set to be restrictive (like 600) and the mapred user can't
> read 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