[
https://issues.apache.org/jira/browse/FLINK-13953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16926374#comment-16926374
]
Gary Yao commented on FLINK-13953:
----------------------------------
Thanks for looking into this, [~zhuzh]. I think it's reasonable to introduce a
cronjob to run a subset of tests against the new scheduler for now. IMO we
still need the {{AlsoRunWithSchedulerNG}} annotation because we have to enable
tests one by one (it is unlikely that all tests will pass in the beginning).
WDYT?
> 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: Zhu Zhu
> 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*
> * Subset of tests using {{MiniCluster}} can be 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)
