[
https://issues.apache.org/jira/browse/HADOOP-6400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12784045#action_12784045
]
Hadoop QA commented on HADOOP-6400:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12426487/hadoop-6400.txt
against trunk revision 885534.
+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 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 passed 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/154/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/154/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/154/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/154/console
This message is automatically generated.
> Log errors getting Unix UGI
> ---------------------------
>
> Key: HADOOP-6400
> URL: https://issues.apache.org/jira/browse/HADOOP-6400
> Project: Hadoop Common
> Issue Type: Improvement
> Components: security
> Affects Versions: 0.20.1, 0.21.0, 0.22.0
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Priority: Minor
> Attachments: hadoop-6400.txt
>
>
> For various reasons, the calls out to `whoami` and `id` can fail when trying
> to get the unix UGI information. Currently it silently ignores failures and
> uses the default DrWho/Tardis ugi. This is extremely confusing for users - we
> should log the exception at warn level when the shell execs fail.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
