[jira] [Commented] (FLINK-9254) Move NotSoMiniClusterIterations to be an end-to-end test

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FLINK-9254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16454301#comment-16454301 ] 

ASF GitHub Bot commented on FLINK-9254:
---------------------------------------

GitHub user azagrebin opened a pull request:

    https://github.com/apache/flink/pull/5921

    [FLINK-9254] Move NotSoMiniClusterIterations to be an end-to-end test

    ## What is the purpose of the change
    
    This PR moves `NotSoMiniClusterIterations` to nightly e2e tests.
    
    ## Brief change log
    
     - submodule `flink-high-parallelism-iterations-test` added to `flink-end-to-end-tests_2.11`
     - `NotSoMiniClusterIterations` moved to `HighParallelismIterationsTestProgram` in `flink-high-parallelism-iterations-test` and factored not to use MiniCluster but run as a normal flink job.
     - `test_high_parallelism_iterations.sh` starts flink cluster with 100 task managers and runs `HighParallelismIterationsTestProgram`
     - `test_high_parallelism_iterations.sh` is added `run-nightly-tests.sh`
    
    ## Verifying this change
    
    - mvn clean -DskipTests package
    - FLINK_DIR=build-target PARALLELISM=10 ./flink-end-to-end-tests/test-scripts/test_high_parallelism_iterations.sh
    
    Real test is set to run 100 task managers by default.
    
    ## 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)
      - 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)


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/azagrebin/flink FLINK-9254

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/flink/pull/5921.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 #5921
    
----
commit 638e7233345742fb085281b202796e4e9e40e7ee
Author: Andrey Zagrebin <an...@...>
Date:   2018-04-26T13:58:09Z

    [FLINK-9254] Move NotSoMiniClusterIterations to be an end-to-end test

----


> Move NotSoMiniClusterIterations to be an end-to-end test
> --------------------------------------------------------
>
>                 Key: FLINK-9254
>                 URL: https://issues.apache.org/jira/browse/FLINK-9254
>             Project: Flink
>          Issue Type: Test
>          Components: Tests
>    Affects Versions: 1.5.0
>            Reporter: Andrey Zagrebin
>            Assignee: Andrey Zagrebin
>            Priority: Minor
>             Fix For: 1.5.0
>
>
> NotSoMiniClusterIterations should be a test that we don’t run for every commit but nightly e2e.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)