[
https://issues.apache.org/jira/browse/FLINK-8073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16407745#comment-16407745
]
ASF GitHub Bot commented on FLINK-8073:
---------------------------------------
Github user StephanEwen commented on the issue:
https://github.com/apache/flink/pull/5718
Having a custom timeout like @zentol suggests could be helpful in the long
run.
For now, though, I personally agree that the timeouts are counter
productive (I actually never understood what they are supposed to solve). I
prefer a deadlocking test to stay around, so I can jstack to the process,
attach a debugger, pull a heap dump, whatever. The only environment where we
cannot do that is the CI server, which has a timeout and thread dump already...
> Test instability
> FlinkKafkaProducer011ITCase.testScaleDownBeforeFirstCheckpoint()
> ---------------------------------------------------------------------------------
>
> Key: FLINK-8073
> URL: https://issues.apache.org/jira/browse/FLINK-8073
> Project: Flink
> Issue Type: Bug
> Components: Kafka Connector, Tests
> Affects Versions: 1.4.0, 1.5.0
> Reporter: Kostas Kloudas
> Priority: Blocker
> Labels: test-stability
> Fix For: 1.5.0
>
>
> Travis log: https://travis-ci.org/kl0u/flink/jobs/301985988
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
