You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by GitBox <gi...@apache.org> on 2019/09/30 06:29:49 UTC

[GitHub] [flink] zhuzhurk opened a new pull request #9819: [FLINK-14246][runtime] Annotate all MiniCluster tests in flink-runtime with AlsoRunWithSchedulerNG

zhuzhurk opened a new pull request #9819: [FLINK-14246][runtime] Annotate all MiniCluster tests in flink-runtime with AlsoRunWithSchedulerNG
URL: https://github.com/apache/flink/pull/9819
 
 
   
   ## What is the purpose of the change
   
   This PR is to annotate all MiniCluster tests with AlsoRunWithSchedulerNG in flink-runtime, so that we can know breaking changes in time when further improving the new generation scheduler.
   This PR also fixes tests that break with DefaultScheduler.
   
   ## Brief change log
   
   *(for example:)*
     - *Annotate all MiniCluster tests with AlsoRunWithSchedulerNG in flink-runtime*
     - *Fix tests that break with DefaultScheduler*
   
   
   ## Verifying this change
   
   For legacy scheduler, this change is already covered by existing tests.
   For DefaultScheduler, this change is verified by manual executing "mvn verify -Dscheduler-ng" locally. It should also be verified by checking the cron job result when the PR of FLINK-14040 is merged.
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): (yes / **no**)
     - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: (yes / **no**)
     - The serializers: (yes / **no** / don't know)
     - The runtime per-record code paths (performance sensitive): (yes / **no** / don't know)
     - Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (yes / **no** / don't know)
     - The S3 file system connector: (yes / **no** / don't know)
   
   ## Documentation
   
     - Does this pull request introduce a new feature? (yes / **no**)
     - If yes, how is the feature documented? (**not applicabl**e / docs / JavaDocs / not documented)
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services