[
https://issues.apache.org/jira/browse/HADOOP-6687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12876373#action_12876373
]
Hadoop QA commented on HADOOP-6687:
-----------------------------------
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12446509/HADOOP-6687.3.patch
against trunk revision 951624.
+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 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/570/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/570/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/570/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/570/console
This message is automatically generated.
> user object in the subject in UGI should be reused in case of a relogin.
> -------------------------------------------------------------------------
>
> Key: HADOOP-6687
> URL: https://issues.apache.org/jira/browse/HADOOP-6687
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Jitendra Nath Pandey
> Assignee: Jitendra Nath Pandey
> Attachments: HADOOP-6687-y20.2.patch, HADOOP-6687.2.patch,
> HADOOP-6687.3.patch
>
>
> In case of a relogin, a new user object is created in the subject. This
> causes the subject to lose some state for example authentication method.
> Instead, a new user object should not be added to the subject if one is
> already present.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
