[ 
https://issues.apache.org/jira/browse/MAPREDUCE-4860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13530589#comment-13530589
 ] 

Hadoop QA commented on MAPREDUCE-4860:
--------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12560688/mr-4860.patch
  against trunk revision .

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: 
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3121//console

This message is automatically generated.
                
> DelegationTokenRenewal attempts to renew token even after a job is removed
> --------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-4860
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4860
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: security
>    Affects Versions: 1.1.1
>            Reporter: Karthik Kambatla
>            Assignee: Karthik Kambatla
>         Attachments: mr-4860.patch, mr-4860.patch, mr-4860.patch, 
> mr-4860.patch
>
>
> mapreduce.security.token.DelegationTokenRenewal synchronizes on 
> removeDelegationToken, but fails to synchronize on addToken, and renewing 
> tokens in run().
> This inconsistency is exposed by frequent failures of 
> TestDelegationTokenRenewal:
> {noformat}
> Error Message
> renew wasn't called as many times as expected expected:<4> but was:<5>
> Stacktrace
> junit.framework.AssertionFailedError: renew wasn't called as many times as 
> expected expected:<4> but was:<5>
>       at 
> org.apache.hadoop.mapreduce.security.token.TestDelegationTokenRenewal.testDTRenewal(TestDelegationTokenRenewal.java:317)
>       at 
> org.apache.hadoop.mapreduce.security.token.TestDelegationTokenRenewal.testDTRenewalAfterClose(TestDelegationTokenRenewal.java:338)
> {noformat}

--
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

Reply via email to