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

Posted to jira@kafka.apache.org by "Greg Harris (Jira)" <ji...@apache.org> on 2024/03/22 17:54:00 UTC

[jira] [Resolved] (KAFKA-16354) FinalizedFeatureChangeListenerTest should use mocked latches

     [ https://issues.apache.org/jira/browse/KAFKA-16354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Greg Harris resolved KAFKA-16354.
---------------------------------
    Resolution: Won't Fix

> FinalizedFeatureChangeListenerTest should use mocked latches
> ------------------------------------------------------------
>
>                 Key: KAFKA-16354
>                 URL: https://issues.apache.org/jira/browse/KAFKA-16354
>             Project: Kafka
>          Issue Type: Test
>          Components: core
>    Affects Versions: 3.7.0
>            Reporter: Greg Harris
>            Priority: Trivial
>              Labels: newbie
>
> testCacheUpdateWaitFailsForUnreachableVersion takes 30 seconds, and testInitFailureDueToFeatureIncompatibility takes 5 seconds. This appears to be caused by FeatureCacheUpdater#awaitUpdateOrThrow waiting for a real CountDownLatch with a real-time timeout.
> Instead, a mocked latch should be used to exit the await immediately.
> This should be done both for CPU-independence, and for test execution speed.



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