[
https://issues.apache.org/jira/browse/FLINK-6744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16047602#comment-16047602
]
Till Rohrmann commented on FLINK-6744:
--------------------------------------
I think the reason for the flakey test is the too aggressive timeout when
verifying that the {{TaskManagerGateway#submitTask}} method has been called.
> 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
> Assignee: Till Rohrmann
> Priority: Critical
> 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)
