[jira] [Updated] (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 updated FLINK-13953:
-
Fix Version/s: 1.10.0
> 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)
[jira] [Updated] (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
]
ASF GitHub Bot updated FLINK-13953:
---
Labels: pull-request-available (was: )
> 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
>
> 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.2#803003)
[jira] [Updated] (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
]
Zhu Zhu updated FLINK-13953:
Description:
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.
was:
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*
* An junit test category {{AlsoRunWithSchedulerNG}} will be used to mark
MiniCluster tests.
* A new maven profile {{ng}} will be enabled to support running
{{AlsoRunWithSchedulerNG}} annotated tests with {{schedulerNG}}.
> 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.
> 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.2#803003)
[jira] [Updated] (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
]
Zhu Zhu updated FLINK-13953:
Description:
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*
* An junit test category {{AlsoRunWithSchedulerNG}} will be used to mark
MiniCluster tests.
* A new maven profile {{ng}} will be enabled to support running
{{AlsoRunWithSchedulerNG}} annotated tests with {{schedulerNG}}.
was:
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 manually against new
scheduler
> 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.
> In the first step the tests should be able to run manually against new
> scheduler.
> *Acceptance Criteria*
> * An junit test category {{AlsoRunWithSchedulerNG}} will be used to mark
> MiniCluster tests.
> * A new maven profile {{ng}} will be enabled to support running
> {{AlsoRunWithSchedulerNG}} annotated tests with {{schedulerNG}}.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (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
]
Zhu Zhu updated FLINK-13953:
Description:
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 manually against new
scheduler
was:
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
> 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 manually against new
> scheduler
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (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 updated FLINK-13953:
-
Description:
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
was:
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
> 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*
> * 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)
