You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Till Rohrmann (JIRA)" <ji...@apache.org> on 2017/06/13 08:33:00 UTC
[jira] [Commented] (FLINK-6744) Flaky ExecutionGraphSchedulingTest
[ https://issues.apache.org/jira/browse/FLINK-6744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16047565#comment-16047565 ]
Till Rohrmann commented on FLINK-6744:
--------------------------------------
Another instance: https://s3.amazonaws.com/archive.travis-ci.org/jobs/242018339/log.txt
> Flaky ExecutionGraphSchedulingTest
> ----------------------------------
>
> Key: FLINK-6744
> URL: https://issues.apache.org/jira/browse/FLINK-6744
> Project: Flink
> Issue Type: Bug
> Components: Tests
> Affects Versions: 1.4.0
> Reporter: Chesnay Schepler
> Labels: test-stability
>
> {code}
> Tests run: 6, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 2.013 sec <<< FAILURE! - in org.apache.flink.runtime.executiongraph.ExecutionGraphSchedulingTest
> testDeployPipelinedConnectedComponentsTogether(org.apache.flink.runtime.executiongraph.ExecutionGraphSchedulingTest) Time elapsed: 0.121 sec <<< FAILURE!
> org.mockito.exceptions.verification.WantedButNotInvoked:
> Wanted but not invoked:
> taskManagerGateway.submitTask(<any>, <any>);
> -> at org.apache.flink.runtime.executiongraph.ExecutionGraphSchedulingTest.testDeployPipelinedConnectedComponentsTogether(ExecutionGraphSchedulingTest.java:246)
> Actually, there were zero interactions with this mock.
> at org.apache.flink.runtime.executiongraph.ExecutionGraphSchedulingTest.testDeployPipelinedConnectedComponentsTogether(ExecutionGraphSchedulingTest.java:246)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)