Github user tillrohrmann commented on the issue:
https://github.com/apache/flink/pull/2450
I've re-introduced the `ForkableFlinkMiniCluster`. However, this time it
only starts the normal distributed component classes (e.g. `JobManager` instead
of `TestingJobManager`, etc.). This implies that the testing messages are no
longer supported when using the `ForkableFlinkMiniCluster`.
I think the user should not meddle with the testing components in the first
place. Therefore, it seems to be fair to offer the user a mini cluster to run
his tests but not one which instantiates testing components. The recommended
cluster is the `LocalFlinkMiniCluster` from now on. However, in order to not
break all existing test code, we still maintain the `ForkableFlinkMiniCluster`.
Not having to start the testing classes allows to move them back into the
test scope of `flink-runtime`, since they are no longer required by the
`flink-test-utils` module.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
