[
https://issues.apache.org/jira/browse/FLINK-14040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Yao updated FLINK-14040:
-----------------------------
Description:
Before making {{SchedulerNG}} the default scheduler, we need to guarantee all
the {{MiniCluster}} tests can pass with it.
FLINK-13953 introduces a way to run existing {{MiniCluster}} tests against
{{SchedulerNG}}.
I'd propose to enable NG scheduler testing in per-commit tests, given that the
travis currently have capacity to run per-commit tests for scheduler NG.
was:
Before making {{SchedulerNG}} the default scheduler, we need to guarantee all
the {{MiniCluster}} tests can pass with it.
FLINK-13953 introduces a way to run existing {{MiniCluster}} tests against
{{SchedulerNG}}.
-To not burden per-commit tests, a cron job should be used to run these tests.-
I'd propose to enable NG scheduler testing in per-commit tests, given that the
travis currently have capacity to run per-commit tests for scheduler NG.
> Enable NG scheduler testing in per-commit tests
> -----------------------------------------------
>
> Key: FLINK-14040
> URL: https://issues.apache.org/jira/browse/FLINK-14040
> Project: Flink
> Issue Type: Sub-task
> Components: Build System, Runtime / Coordination
> Affects Versions: 1.10.0
> Reporter: Zhu Zhu
> Assignee: Zhu Zhu
> Priority: Major
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Before making {{SchedulerNG}} the default scheduler, we need to guarantee all
> the {{MiniCluster}} tests can pass with it.
> FLINK-13953 introduces a way to run existing {{MiniCluster}} tests against
> {{SchedulerNG}}.
> I'd propose to enable NG scheduler testing in per-commit tests, given that
> the travis currently have capacity to run per-commit tests for scheduler NG.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
