[
https://issues.apache.org/jira/browse/FLINK-1660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14352772#comment-14352772
]
Jonas Traub commented on FLINK-1660:
------------------------------------
Hi,
Just a few words about what this test does:
This test verifies, whether separated threads start up correctly or not. In
case time-based window discretisation is used, we use separated threads to
cause the emission of results for windows, even if no data-item arrives within
the duration of a window. The test expects three such threads to start up and
to confirm their startup thew a callback method. If they don't reply within 10
sec. the test fails.
Increasing the timeout might be indeed a good and simple solution. The question
is whether it solves the problem or not. An alternative would be to remove the
timeout, but then the test possibly runs infinitely instead of failing after a
while.
As I cannot reproduce the problem you described (because in my case the test
succeeds), can you be so kind and just increase the value for the timeout in
code line 142 of MultiTriggerPolicyTest and test whether it solves the problem
or not?
> 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
>
> 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)
