[
https://issues.apache.org/jira/browse/FLINK-1660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14492239#comment-14492239
]
ASF GitHub Bot commented on FLINK-1660:
---------------------------------------
GitHub user uce opened a pull request:
https://github.com/apache/flink/pull/590
[FLINK-1660] [streaming] [tests] Fix MultiTriggerPolicyTest race
Waiting for Travis and a short look over this won't hurt. ;-)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/uce/incubator-flink trigger-1660
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/590.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 #590
----
commit d1cb1cbb4d28ace1232d32b3c3a79e13cc3477b8
Author: Ufuk Celebi <[email protected]>
Date: 2015-04-13T10:16:16Z
[FLINK-1660] [streaming] [tests] Fix MultiTriggerPolicyTest race
----
> MultiTriggerPolicyTest timeout during test
> ------------------------------------------
>
> Key: FLINK-1660
> URL: https://issues.apache.org/jira/browse/FLINK-1660
> Project: Flink
> Issue Type: Bug
> Components: Streaming
> Reporter: Ufuk Celebi
> Priority: Minor
> Fix For: 0.9
>
>
> Running tests through Maven locally, I encountered a timeout in
> MultiTriggerPolicyTest#testActiveTriggerRunnables
> saying that it timed out after 10s.
> I've looked into the code and saw that it is almost totally unrelated to the
> runtime. I therefore suspect that it was due to a system hickup. Could
> someone please confirm this and maybe increase the timeout?
> In general, we should consider setting these timeouts rather high (due to
> Travis etc.)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
