You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flink.apache.org by "Till Rohrmann (JIRA)" <ji...@apache.org> on 2019/06/06 09:39:00 UTC

[jira] [Created] (FLINK-12768) FlinkKinesisConsumerTest.testSourceSynchronization unstable on Travis

Till Rohrmann created FLINK-12768:
-------------------------------------

             Summary: 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
             Fix For: 1.9.0


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 locking 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.3#76005)