GitHub user uce opened a pull request:
https://github.com/apache/flink/pull/2786
[FLINK-5016] [ci] Increase no output timeout to 10 mins
Some heavy test suites occasionally have quite long running times on
Travis, in which cases the no output timeout of 5 mins is too aggressive and
incorrectly fails the build. This behaviour is meant to help debugging any
deadlock situations we encounter on Travis.
This PR increases the no output timeout to 10 minutes. Since we're quite
close to the maximum build times this will not detect anything that deadlocks
in the last 10 minutes of the build after which Travis errors the build. I
think that's OK.
Do you think increasing the timeout is OK or should we instead add some
output to the heavy test suites or split them up?
/cc @tillrohrmann @aljoscha
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/uce/flink 5016-eventtime_test
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/2786.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 #2786
----
commit 64b91d3fcee4c389aced1152d62b9b1a8a3ef69f
Author: Ufuk Celebi <[email protected]>
Date: 2016-11-11T08:47:26Z
[FLINK-5016] [ci] Increase no output timeout to 10 mins
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
