flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "vinoyang (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (FLINK-8931) TASK_KILLING is not covered by match in TaskMonitor#whenUnhandled
Date Thu, 22 Mar 2018 01:38:00 GMT

     [ https://issues.apache.org/jira/browse/FLINK-8931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

vinoyang reassigned FLINK-8931:
-------------------------------

    Assignee: vinoyang

> 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
>            Assignee: vinoyang
>            Priority: Major
>
> 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)

Mime
View raw message