GitHub user NicoK opened a pull request: https://github.com/apache/flink/pull/4571
[FLINK-7487][tests] fix ClassLoaderITCase#testDisposeSavepointWithCustomKvState not self-contained ## What is the purpose of the change The cancellation of the job started in `ClassLoaderITCase#testDisposeSavepointWithCustomKvState()` may actually continue after the test method succeeds and may thus stop further jobs from being executed. This may result in a `NoResourceAvailableException`. ## Brief change log - wait for the execution to finish in `ClassLoaderITCase#testDisposeSavepointWithCustomKvState()` ## Verifying this change This change is fixing a unit test. ## 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, Yarn/Mesos, ZooKeeper: (no) ## Documentation - Does this pull request introduce a new feature? (no) - If yes, how is the feature documented? (not applicable) You can merge this pull request into a Git repository by running: $ git pull https://github.com/NicoK/flink flink-7487 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/flink/pull/4571.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #4571 ---- commit fb32ff1aed2707cdc17bc3e422aa4590b8599a56 Author: Nico Kruber <n...@data-artisans.com> Date: 2017-08-21T15:20:30Z [FLINK-7487][tests] fix ClassLoaderITCase#testDisposeSavepointWithCustomKvState not self-contained The cancellation of the job started in #testDisposeSavepointWithCustomKvState may actually continue after the test method succeeds and may thus stop further jobs from being executed. This may result in a NoResourceAvailableException. ---- --- 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 infrastruct...@apache.org or file a JIRA ticket with INFRA. ---