[
https://issues.apache.org/jira/browse/FLINK-1660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14352821#comment-14352821
]
Ufuk Celebi commented on FLINK-1660:
------------------------------------
It is not reproducible by just running it. It only occurred once during a local
Maven verify run. This is exactly the thing with the timeouts: its mostly fine,
except for cases when it is not. ;) In this case, it was most likely due to the
high load on my system (mutliple JVM forks running the tests etc.) and not an
actual problem. The timings are just different depending on the load of the
system and 10s might not be enough.
If it ever really gets stuck it's easy to debug locally (jps and jstack) and
also on Travis, which does this for stalled builds.
> 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)
