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

ASF GitHub Bot commented on HADOOP-19155:
-----------------------------------------

github-actions[bot] commented on PR #6766:
URL: https://github.com/apache/hadoop/pull/6766#issuecomment-3342139940

   We're closing this stale PR because it has been open for 100 days with no 
activity. This isn't a judgement on the merit of the PR in any way. It's just a 
way of keeping the PR queue manageable.
   If you feel like this was a mistake, or you would like to continue working 
on it, please feel free to re-open it and ask for a committer to remove the 
stale tag and review again.
   Thanks all for your contribution.




> Fix TestZKSignerSecretProvider failing unit test
> ------------------------------------------------
>
>                 Key: HADOOP-19155
>                 URL: https://issues.apache.org/jira/browse/HADOOP-19155
>             Project: Hadoop Common
>          Issue Type: Test
>          Components: auth
>    Affects Versions: 3.4.0
>            Reporter: kuper
>            Priority: Minor
>              Labels: pull-request-available
>         Attachments: 企业微信截图_4436de68-18c5-43bf-9382-4d9a853f7ef0.png, 
> 企业微信截图_ab901a4a-c0d4-4a20-a595-057cf648c30c.png, 
> 企业微信截图_fa5e7d54-b3a8-4ca3-8d4a-25fe493b4eb1.png
>
>
> * {{TestZKSignerSecretProvider and 
> }}{{{}TestRandomSignerSecretProvider{}}}{{{{}} unit test o{}}}ccasional 
> failure
>  * The reason was that the MockZKSignerSecretProvider class rollSecret method 
> is {{synchronized}}
>  * {{{}s{}}}ometimes verify (secretProvider, timeout (timeout). AtLeastOnce 
> ()). RollSecret () method first in RolloverSignerSecretProvider scheduler 
> thread lock, this results in a timeout
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to