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

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

GitHub user rmetzger opened a pull request:

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

    FLINK-5731 Spilt up tests into three disjoint groups

    We were running into build timeouts again recently on travis.
    That's why I've split the tests into three groups (instead of two).
    
    This means we'll have 12 test jobs (5 run concurrently)
    
    
![image](https://cloud.githubusercontent.com/assets/89049/23065154/535d482e-f514-11e6-904a-96b124a53863.png)
    
    I'm not sure if we want to merge this or not. It gives us only 10 more 
minutes on the slowest builds, so we'll run into the issue again at some point.


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

    $ git pull https://github.com/rmetzger/flink flink5731

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

    https://github.com/apache/flink/pull/3344.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 #3344
    
----
commit b242b3838695805e191fad55684b05c779084897
Author: Robert Metzger <rmetz...@apache.org>
Date:   2017-02-13T20:43:25Z

    FLINK-5731 Spilt up tests into three disjoint groups

----


> Split up CI builds
> ------------------
>
>                 Key: FLINK-5731
>                 URL: https://issues.apache.org/jira/browse/FLINK-5731
>             Project: Flink
>          Issue Type: Improvement
>          Components: Build System, Tests
>            Reporter: Ufuk Celebi
>            Assignee: Robert Metzger
>            Priority: Critical
>
> Test builds regularly time out because we are hitting the Travis 50 min 
> limit. Previously, we worked around this by splitting up the tests into 
> groups. I think we have to split them further.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to