[
https://issues.apache.org/jira/browse/FLINK-15582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhu Zhu updated FLINK-15582:
----------------------------
Comment: was deleted
(was: [~trohrmann] this is a pre-requisite for removing LegacyScheduler but I
think it is also a needed test for DefaultScheduler in 1.10.
To be detailed, I plan to extract most of the codes in
{{LegacySchedulerBatchSchedulingTest}} to a {{BatchSchedulingTestBase}} and
then let the implementations {{LegacySchedulerBatchSchedulingTest}} and
{{DefaultSchedulerBatchSchedulingTest}} implement the {{createScheduler(...)}}
method only. So later when removing the LegacyScheduler we can just remove
{{LegacySchedulerBatchSchedulingTest}} as well.
WDYT?)
> Enable batch scheduling tests in LegacySchedulerBatchSchedulingTest for
> DefaultScheduler as well
> ------------------------------------------------------------------------------------------------
>
> Key: FLINK-15582
> URL: https://issues.apache.org/jira/browse/FLINK-15582
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Coordination
> Affects Versions: 1.10.0, 1.11.0
> Reporter: Zhu Zhu
> Assignee: Zhu Zhu
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.11.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {{testSchedulingOfJobWithFewerSlotsThanParallelism}} is a common case but it
> is only tested with legacy scheduler in
> {{LegacySchedulerBatchSchedulingTest}} at the moment.
> We should enable it for DefaultScheduler as well.
> This also allows us to safely remove {{LegacySchedulerBatchSchedulingTest}}
> when we are removing the LegacyScheduler and related components without
> loosing test coverage.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
