[
https://issues.apache.org/jira/browse/FLINK-7011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16069444#comment-16069444
]
ASF GitHub Bot commented on FLINK-7011:
---------------------------------------
Github user tzulitai commented on the issue:
https://github.com/apache/flink/pull/4190
@zentol the time limit is set on each individual version-specific
`KafkaConsumerXXITCase`
> Instable Kafka testStartFromKafkaCommitOffsets failures on Travis
> -----------------------------------------------------------------
>
> Key: FLINK-7011
> URL: https://issues.apache.org/jira/browse/FLINK-7011
> Project: Flink
> Issue Type: Bug
> Components: Kafka Connector, Tests
> Affects Versions: 1.3.1, 1.4.0
> Reporter: Tzu-Li (Gordon) Tai
> Assignee: Tzu-Li (Gordon) Tai
>
> Example:
> https://s3.amazonaws.com/archive.travis-ci.org/jobs/246703474/log.txt?X-Amz-Expires=30&X-Amz-Date=20170627T065647Z&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAJRYRXRSVGNKPKO5A/20170627/us-east-1/s3/aws4_request&X-Amz-SignedHeaders=host&X-Amz-Signature=dbfc90cfc386fef0990325b54ff74ee4d441944687e7fdaa73ce7b0c2b2ec0ea
> In general, the test {{testStartFromKafkaCommitOffsets}} implementation is a
> bit of an overkill. Before continuing with the test, it writes some records
> just for the sake of committing offsets to Kafka and waits for some offsets
> to be committed (which leads to the instability), whereas we can do that
> simply using the test base's {{OffsetHandler}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)