flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sachin Goel (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-2852) Fix flaky ScalaShellITSuite
Date Mon, 19 Oct 2015 18:19:05 GMT

    [ https://issues.apache.org/jira/browse/FLINK-2852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14963722#comment-14963722

Sachin Goel commented on FLINK-2852:

I was working on a fix. Here's the code: https://github.com/sachingoel0101/flink/tree/flink-2852
If you haven't worked on it yet, I can open a PR from my branch.

> 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

This message was sent by Atlassian JIRA

View raw message