[
https://issues.apache.org/jira/browse/MAPREDUCE-4633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13449092#comment-13449092
]
Hadoop QA commented on MAPREDUCE-4633:
--------------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12543868/MAPREDUCE-4633.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-common
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/2818//testReport/
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2818//console
This message is automatically generated.
> history server doesn't set permissions on all subdirs
> ------------------------------------------------------
>
> Key: MAPREDUCE-4633
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4633
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: jobhistoryserver
> Affects Versions: 0.23.3, 3.0.0, 2.2.0-alpha
> Reporter: Thomas Graves
> Assignee: Thomas Graves
> Priority: Critical
> Attachments: MAPREDUCE-4633.patch
>
>
> The job history server creates a bunch of subdirectories under the "done"
> directory. They are like 2012/09/03/000000. It only sets the permissions on
> the last one, ie 000000 to 770. So the 2012/09/03 aren't explicitly set so
> if the umask is more restrictive, they won't be set as it expects.
--
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
