Skip to content

Conversation

@mateczagany
Copy link
Contributor

What is the purpose of the change

This fix is related to PR #26821 and sometimes these tests fail because the scheduler is being called from outside the main class.

Brief change log

  • Set up executor for JM main thread and use that to interact with the Scheduler in ExecutionPartitionLifecycleTest

Verifying this change

After this change, I could no longer reproduce the failure

Does this pull request potentially affect one of the following parts:

  • Dependencies (does it add or upgrade a dependency): no
  • The public API, i.e., is any changed class annotated with @Public(Evolving): no
  • The serializers: no
  • The runtime per-record code paths (performance sensitive): no
  • Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
  • The S3 file system connector: no

Documentation

  • Does this pull request introduce a new feature? no
  • If yes, how is the feature documented? not applicable

@flinkbot
Copy link
Collaborator

flinkbot commented Jan 13, 2026

CI report:

Bot commands The @flinkbot bot supports the following commands:
  • @flinkbot run azure re-run the last Azure build

@mateczagany mateczagany changed the title [FLINK-38903] Fix flaky ExecutionPartitionLifecycleTest [FLINK-38908] Fix flaky ExecutionPartitionLifecycleTest Jan 13, 2026
@mateczagany
Copy link
Contributor Author

@flinkbot run azure

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants