[
https://issues.apache.org/jira/browse/FLINK-7259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16492633#comment-16492633
]
Alexandr Arkhipov commented on FLINK-7259:
------------------------------------------
This one has already been resolved by FLINK-8931
> Match not exhaustive in TaskMonitor
> -----------------------------------
>
> Key: FLINK-7259
> URL: https://issues.apache.org/jira/browse/FLINK-7259
> Project: Flink
> Issue Type: Bug
> Components: Mesos
> Affects Versions: 1.3.1, 1.4.0
> Reporter: Till Rohrmann
> Priority: Major
>
> Two matches are not exhaustive in the class {{TaskMonitor}}. This can lead to
> a {{MatchError}}, potentially restarting this actor (depending on the
> supervision strategy).
> {code}
>
> /Users/uce/Code/flink/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]
> /Users/uce/Code/flink/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 {
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
