[
https://issues.apache.org/jira/browse/FLINK-21604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-21604:
-----------------------------------
Labels: stale-major (was: )
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Major but is unassigned and neither itself nor its Sub-Tasks have been updated
for 30 days. I have gone ahead and added a "stale-major" to the issue". If this
ticket is a Major, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> Remove adaptive scheduler nightly test profile, replace with more specific
> testing approach
> -------------------------------------------------------------------------------------------
>
> Key: FLINK-21604
> URL: https://issues.apache.org/jira/browse/FLINK-21604
> Project: Flink
> Issue Type: Technical Debt
> Components: Runtime / Coordination
> Reporter: Robert Metzger
> Priority: Major
> Labels: stale-major
>
> We are currently running all tests with the adaptive scheduler, but only once
> a night.
> This is wasteful for all tests not using any scheduler.
> Ideally, we come up with a testing strategy where we run all relevant tests
> (checkpointing, failure, recovery, .. etc. related with both schedulers.
> One approach would be parameterizing some tests.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
