[
https://issues.apache.org/jira/browse/FLINK-39414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18073435#comment-18073435
]
Taranpreet Kaur commented on FLINK-39414:
-----------------------------------------
Hi [~mapohl]
Can you please verify if approach is right or not :
I think issue is each test depends on the duration and longDuration fields
which can be reduced dramatically. The test just needs to prove a future
doesn't complete
within a window — it doesn't need 15s/30s for that.
So, we can reduce this time to 200ms to 300ms.
> TaskExecutorPartitionLifecycleTest#testEnableBatchJobRecoveryAnd* take long
> time to complete
> --------------------------------------------------------------------------------------------
>
> Key: FLINK-39414
> URL: https://issues.apache.org/jira/browse/FLINK-39414
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Coordination
> Affects Versions: 2.0.1, 2.2.0, 2.1.1
> Reporter: Matthias Pohl
> Priority: Minor
> Labels: test-stability
>
> There are two test methods in {{TaskExecutorPartitionLifecycleTest}} which
> take quite long to finish:
> * {{testEnableBatchJobRecoveryAndNotRetainPartitions}} takes 15s
> * {{testEnableBatchJobRecoveryAndRetainPartitions}} takes 30s
> We might want to look into why they take that long and maybe add some
> improvement here to speed up CI.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
