You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "Alexandre Dupriez (Jira)" <ji...@apache.org> on 2023/03/06 11:20:00 UTC

[jira] [Commented] (KAFKA-14780) Make RefreshingHttpsJwksTest#testSecondaryRefreshAfterElapsedDelay deterministic

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

Alexandre Dupriez commented on KAFKA-14780:
-------------------------------------------

[~kirktrue], would you agree with the approach? This requires a minor change in  `RefreshingHttpsJwks` to expose the scheduler that it uses. Thanks!

> Make RefreshingHttpsJwksTest#testSecondaryRefreshAfterElapsedDelay deterministic
> --------------------------------------------------------------------------------
>
>                 Key: KAFKA-14780
>                 URL: https://issues.apache.org/jira/browse/KAFKA-14780
>             Project: Kafka
>          Issue Type: Test
>            Reporter: Alexandre Dupriez
>            Priority: Minor
>
> The test `RefreshingHttpsJwksTest#testSecondaryRefreshAfterElapsedDelay` relies on the actual system clock which makes it frequently fail on my poor intellij setup.
>  
> The `RefreshingHttpsJwks` component creates and uses a scheduled executor service. We could expose the scheduling mechanism to be able to mock its behaviour. One way to do could be to use the `KafkaScheduler` which has a `MockScheduler` implementation which relies on `MockTime` instead of the real time clock.



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