[
https://issues.apache.org/jira/browse/FLINK-13953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16922240#comment-16922240
]
Gary Yao commented on FLINK-13953:
----------------------------------
There exists a prototype by [~till.rohrmann]
https://github.com/tillrohrmann/flink/tree/introduceSchedulerSwitch
Another possibility that I can think of is to use Junit's parameterized tests.
> Facilitate enabling new Scheduler in MiniCluster Tests
> ------------------------------------------------------
>
> Key: FLINK-13953
> URL: https://issues.apache.org/jira/browse/FLINK-13953
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / Coordination, Tests
> Reporter: Gary Yao
> Assignee: Gary Yao
> Priority: Major
>
> Currently, tests using the {{MiniCluster}} use the legacy scheduler by
> default. Once the new scheduler is implemented, we should run tests with the
> new scheduler enabled. However, it is not expected that all tests will pass
> immediately. Therefore, it should be possible to enable the new scheduler for
> a subset of tests.
> *Acceptance Criteria*
> * Tests using {{MiniCluster}} are run on a per-commit basis (on Travis)
> against new scheduler and also legacy scheduler
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
