[
https://issues.apache.org/jira/browse/FLINK-12768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16886413#comment-16886413
]
Thomas Weise commented on FLINK-12768:
--------------------------------------
I opened a PR hoping to be able to reproduce this on Travis with additional
information. Unable to do so locally.
> FlinkKinesisConsumerTest.testSourceSynchronization unstable on Travis
> ---------------------------------------------------------------------
>
> Key: FLINK-12768
> URL: https://issues.apache.org/jira/browse/FLINK-12768
> Project: Flink
> Issue Type: Bug
> Components: Connectors / Kinesis
> Affects Versions: 1.9.0
> Reporter: Till Rohrmann
> Assignee: Thomas Weise
> Priority: Critical
> Labels: pull-request-available, test-stability
> Fix For: 1.9.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The {{FlinkKinesisConsumerTest.testSourceSynchronization}} seems to be
> unstable on Travis. It fails with
> {code}
> [ERROR]
> testSourceSynchronization(org.apache.flink.streaming.connectors.kinesis.FlinkKinesisConsumerTest)
> Time elapsed: 10.031 s <<< FAILURE!
> java.lang.AssertionError:
> Expected: iterable containing ["1", <Watermark @ -4>]
> but: No item matched: <Watermark @ -4>
> at
> org.apache.flink.streaming.connectors.kinesis.FlinkKinesisConsumerTest.testSourceSynchronization(FlinkKinesisConsumerTest.java:950)
> {code}
> https://api.travis-ci.org/v3/job/541845510/log.txt
> While looking into the problem, I noticed that the test case takes 1 second
> to execute on my machine. I'm wondering whether this really needs to take
> this long. Moreover, the test code contains {{Thread.sleeps}} and uses
> {{Whiteboxing}} which we should avoid.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
