[FLINK-39414] TaskExecutorPartitionLifecycleTest#testEnableBatchJobRecoveryAnd* take long time to complete#27930
[FLINK-39414] TaskExecutorPartitionLifecycleTest#testEnableBatchJobRecoveryAnd* take long time to complete#27930HundalTaran wants to merge 3 commits intoapache:masterfrom
Conversation
…e long time to complete
There was a problem hiding this comment.
@HundalTaran Can you add the Jira ID to the PR [FLINK-39414] in place of Issue.
Help in linking up.
Thanks made the changes |
I have checked the logs, it does not seems like that failure is due to my changes: failure reason: 2026-04-15T06:57:58.6124653Z Apr 15 06:57:58 06:57:58.607 [INFO] ------------------------------------------------------------------------ |
|
@flinkbot run azure |
e8ffe12 to
96db245
Compare
spuru9
left a comment
There was a problem hiding this comment.
Thank you for the change.
LGTM +1
|
@flinkbot run azure |
1 similar comment
|
@flinkbot run azure |
|
@flinkbot run azure |


What is the purpose of the change
There are two test methods in TaskExecutorPartitionLifecycleTest which take quite long to finish:
testEnableBatchJobRecoveryAndNotRetainPartitions takes 15s
testEnableBatchJobRecoveryAndRetainPartitions takes 30s
Brief change log
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 completewithin a window — it doesn't need 15s/30s for that.
So reduced the duration to 200ms and 300ms respectively.
private Duration duration = Duration.ofMillis(200);
private Duration longDuration = Duration.ofMillis(300);
Verifying this change
The changes are verified by running this test class multiple times.
Does this pull request potentially affect one of the following parts:
@Public(Evolving): (yes / no) - noDocumentation