[jira] [Resolved] (FLINK-3350) Increase timeouts on Travis Builds

["Stephan Ewen (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/FLINK-3350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stephan Ewen resolved FLINK-3350.
---------------------------------
    Resolution: Fixed

Fixed via b8f40251c6c45379118254c21b0d553c2d3b8937

> Increase timeouts on Travis Builds
> ----------------------------------
>
>                 Key: FLINK-3350
>                 URL: https://issues.apache.org/jira/browse/FLINK-3350
>             Project: Flink
>          Issue Type: Bug
>          Components: Tests
>    Affects Versions: 1.0.0
>            Reporter: Stephan Ewen
>            Assignee: Ufuk Celebi
>            Priority: Critical
>             Fix For: 1.0.0
>
>
> We see a lot of failures on Travis because of Timeouts.
> I think the problem is simply that the default ask timeouts of "10 seconds" is too short to reliably execute tests in parallel on the small containers on Travis, especially when many services (like zookeeper mini clusters, etc) are involved. The tests work most of the time, but with the large amount of tests we have, builds fail if 1 out of 1000 tests experiences a timeout.
> I suggest that we change the {{ForkableMiniCluster}} such that it multiplies the default timeout by a factor from an environment variable, which we set in the travis build scripts.
> Something like {{export TEST_TIMEOUT_FACTOR=3}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)