This is an automated email from the ASF dual-hosted git repository. kkloudas pushed a change to branch executors-clean in repository https://gitbox.apache.org/repos/asf/flink.git.
discard 58b988d [TRAVIS] Removed notifications discard 00e7860 [FLINK-XXXXX] Remove redundant CliFrontend.runProgram() method discard effbde3 [FLINK-XXXXX] Refactoring the ContextEnvironments new 051b9ed [FLINK-XXXXX] Refactoring the ContextEnvironments new 044645b [FLINK-XXXXX] Fix completeness tests new f9c967f [FLINK-XXXXX] Remove redundant CliFrontend.runProgram() method new 75427d3 [TRAVIS] Removed notifications This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (58b988d) \ N -- N -- N refs/heads/executors-clean (75427d3) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. The 4 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: .../java/org/apache/flink/client/cli/AbstractCustomCommandLine.java | 3 ++- .../dataset/tests/test_execution_environment_completeness.py | 3 ++- .../flink/streaming/api/environment/StreamExecutionEnvironment.java | 4 ---- .../api/scala/completeness/BatchScalaAPICompletenessTest.scala | 3 +++ .../main/java/org/apache/flink/yarn/cli/FlinkYarnSessionCli.java | 6 +++++- 5 files changed, 12 insertions(+), 7 deletions(-)