You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Gary Yao (Jira)" <ji...@apache.org> on 2019/09/19 14:02:00 UTC

[jira] [Resolved] (FLINK-13953) Facilitate enabling new Scheduler in MiniCluster Tests

     [ https://issues.apache.org/jira/browse/FLINK-13953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Yao resolved FLINK-13953.
------------------------------
    Resolution: Fixed

1.10: 34b5399f4effb679baabd8bca312cbf92ec34165

> 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
>              Labels: pull-request-available
>             Fix For: 1.10.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> 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. 
> In the first step the tests should be able to run manually against new scheduler.
> *Acceptance Criteria*
>  * A junit test category {{AlsoRunWithSchedulerNG}} can be used to mark MiniCluster tests.
>  * A new maven profile {{scheduler-ng}} will be enabled to support running {{AlsoRunWithSchedulerNG}} annotated tests with the new scheduler.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)