You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Rui Fan (Jira)" <ji...@apache.org> on 2026/08/27 18:29:00 UTC
[jira] [Created] (FLINK-40484) Run UnalignedCheckpointTestBase with DefaultScheduler instead of skipping it under AdaptiveScheduler
Rui Fan created FLINK-40484:
-------------------------------
Summary: Run UnalignedCheckpointTestBase with DefaultScheduler instead of skipping it under AdaptiveScheduler
Key: FLINK-40484
URL: https://issues.apache.org/jira/browse/FLINK-40484
Project: Flink
Issue Type: Technical Debt
Components: Runtime / Checkpointing, Tests
Reporter: Rui Fan
Assignee: Rui Fan
UnalignedCheckpointTestBase is annotated with @Category(FailsWithAdaptiveScheduler) (added in FLINK-21101). When the enable-adaptive-scheduler profile is active, surefire excludes this category, so the whole suite is skipped entirely rather than run.
These are exactly the kind of tests that benefit from being exercised as often as possible — the more they run, the more likely intermittent issues surface. Skipping the suite whenever the adaptive-scheduler profile is on unnecessarily reduces how often it runs and lowers coverage.
Since the suite is only expected to fail under the AdaptiveScheduler (not with the DefaultScheduler), we don't need to skip it. Instead we can pin JobManagerOptions.SCHEDULER = Default in the test's job configuration and drop the category exclusion. The suite then always runs with the DefaultScheduler, regardless of which scheduler the CI profile selects — increasing coverage and giving more chances to catch flakiness, without ever running it under the unsupported AdaptiveScheduler.
Proposed change:
- Set JobManagerOptions.SCHEDULER = Default in UnalignedCheckpointTestBase#getConfiguration.
- Remove @Category(FailsWithAdaptiveScheduler) and the now-unused imports.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)