[
https://issues.apache.org/jira/browse/FLINK-2180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14577109#comment-14577109
]
Márton Balassi commented on FLINK-2180:
---------------------------------------
Usually in similar situations simply increasing the wait time helps a lot in
stabilizing the test. However here I do not see that as a feasible solution as
this also controls when the test actually finishes. If you do not breaking the
existing API, but rather extend it I also think that this is the best approach
that we have currently.
> Streaming iterate test fails spuriously
> ---------------------------------------
>
> Key: FLINK-2180
> URL: https://issues.apache.org/jira/browse/FLINK-2180
> Project: Flink
> Issue Type: Bug
> Components: Streaming
> Affects Versions: 0.9
> Reporter: Márton Balassi
> Assignee: Gábor Hermann
>
> Following output seen occasionally:
> Tests run: 3, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 3.667 sec <<<
> FAILURE! - in org.apache.flink.streaming.api.IterateTest
> test(org.apache.flink.streaming.api.IterateTest) Time elapsed: 3.662 sec
> <<< FAILURE!
> java.lang.AssertionError: null
> at org.junit.Assert.fail(Assert.java:86)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.junit.Assert.assertTrue(Assert.java:52)
> at org.apache.flink.streaming.api.IterateTest.test(IterateTest.java:154)
> See: https://travis-ci.org/mbalassi/flink/jobs/65803465
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
