[
https://issues.apache.org/jira/browse/HADOOP-6396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12782756#action_12782756
]
Hadoop QA commented on HADOOP-6396:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12426184/HADOOP-6396.patch
against trunk revision 883206.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 3 new or modified tests.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
-1 core tests. The patch failed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/150/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/150/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/150/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/150/console
This message is automatically generated.
> Provide a description in the exception when an error is encountered parsing
> umask
> ---------------------------------------------------------------------------------
>
> Key: HADOOP-6396
> URL: https://issues.apache.org/jira/browse/HADOOP-6396
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs
> Affects Versions: 0.21.0, 0.22.0
> Reporter: Jakob Homan
> Assignee: Jakob Homan
> Fix For: 0.21.0, 0.22.0
>
> Attachments: HADOOP-6396.patch
>
>
> Currently when there is a problem parsing a umask, the exception text is just
> the offending umask with no other clue, which can be quite confusing as
> demonstrated in HDFS-763. This message should include the nature of the
> problem and whether or not the umask parsing attempt was using old-style or
> new-style values.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
