[
https://issues.apache.org/jira/browse/HADOOP-6913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12903663#action_12903663
]
Hadoop QA commented on HADOOP-6913:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12451830/c6913-01.patch
against trunk revision 989999.
+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 appears to have generated 1 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-h9.grid.sp2.yahoo.net/40/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h9.grid.sp2.yahoo.net/40/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h9.grid.sp2.yahoo.net/40/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h9.grid.sp2.yahoo.net/40/console
This message is automatically generated.
> Circular initialization between UserGroupInformation and KerberosName
> ---------------------------------------------------------------------
>
> Key: HADOOP-6913
> URL: https://issues.apache.org/jira/browse/HADOOP-6913
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Reporter: Kan Zhang
> Assignee: Kan Zhang
> Attachments: c6913-01.patch
>
>
> If the first call to UGI is UGI.setConfiguration(conf), it will try to
> initialize UGI class. During this initialization, the code calls
> KerberosName.setConfiguration(). KerberosName's static initializer will in
> turn call UGI.isSecurityEnabled(). Since UGI hasn't been completely
> initialized yet, isSecurityEnabled() will re-initialize UGI with a DEFAULT
> conf. As a result, the original conf used in UGI.setConfiguration(conf) will
> be overwritten by the DEFAULT conf.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
