[
https://issues.apache.org/jira/browse/FLINK-2852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14964757#comment-14964757
]
Till Rohrmann commented on FLINK-2852:
--------------------------------------
Hi [~sachingoel0101], you're right that the test is not robust. I've reworked
and pushed a commit which should hopefully solve the problem.
> Fix flaky ScalaShellITSuite
> ---------------------------
>
> Key: FLINK-2852
> URL: https://issues.apache.org/jira/browse/FLINK-2852
> Project: Flink
> Issue Type: Bug
> Components: Scala Shell
> Affects Versions: 0.10
> Reporter: Till Rohrmann
> Assignee: Till Rohrmann
> Priority: Critical
> Labels: test-stability
> Fix For: 0.10
>
>
> The {{ScalaShellITSuite}} checks the log output whether a job has successful
> completed or not. For that to happen it checks for a {{Job execution switched
> to status FINISHED}} string in the log output. However, if the
> {{FlinkClientActor}} receives first a {{JobResultSuccess}} message before
> receiving the {{JobStatusChanged}} message, then it will send the execution
> result back to the {{Client}} and terminate itself. This has the consequence
> that the output will never contain the above-mentioned string.
> I propose to use a different mean to check whether a job has finished
> successfully or not.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
