You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@flink.apache.org by "Ted Yu (JIRA)" <ji...@apache.org> on 2018/03/12 19:30:00 UTC

[jira] [Created] (FLINK-8931) TASK_KILLING is not covered by match in TaskMonitor#whenUnhandled

Ted Yu created FLINK-8931:
-----------------------------

             Summary: TASK_KILLING is not covered by match in TaskMonitor#whenUnhandled
                 Key: FLINK-8931
                 URL: https://issues.apache.org/jira/browse/FLINK-8931
             Project: Flink
          Issue Type: Bug
            Reporter: Ted Yu


Noticed the following :
{code}
[WARNING] /a/flink-1.3.3/flink-mesos/src/main/scala/org/apache/flink/mesos/scheduler/TaskMonitor.scala:157: warning: match may not be exhaustive.
[WARNING] It would fail on the following input: TASK_KILLING
[WARNING]       msg.status().getState match {
[WARNING]                    ^
[WARNING] /a/flink-1.3.3/flink-mesos/src/main/scala/org/apache/flink/mesos/scheduler/TaskMonitor.scala:170: warning: match may not be exhaustive.
[WARNING] It would fail on the following input: TASK_KILLING
[WARNING]       msg.status().getState match {
[WARNING]                    ^
{code}
It seems that TASK_KILLING should be covered by the last case.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)