[
https://issues.apache.org/jira/browse/MESOS-8076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yan Xu reassigned MESOS-8076:
-----------------------------
Assignee: Yan Xu
> PersistentVolumeTest.SharedPersistentVolumeRescindOnDestroy is flaky.
> ---------------------------------------------------------------------
>
> Key: MESOS-8076
> URL: https://issues.apache.org/jira/browse/MESOS-8076
> Project: Mesos
> Issue Type: Bug
> Components: test
> Affects Versions: 1.5.0
> Reporter: Alexander Rukletsov
> Assignee: Yan Xu
> Labels: flaky, flaky-test
> Attachments: SharedPersistentVolumeRescindOnDestroy-badrun.txt,
> SharedPersistentVolumeRescindOnDestroy-goodrun.txt
>
>
> I'm observing
> {{ROOT_MountDiskResource/PersistentVolumeTest.SharedPersistentVolumeRescindOnDestroy/0}}
> being flaky on our internal CI. From what I see in the logs, when
> {{framework1}} accepts an offer, creates volumes, launches a task, and kills
> it right after, the executor might manage to register in-between and hence an
> unexpected {{TASK_RUNNING}} status update is sent. To fix this, one approach
> is to explicitly wait for {{TASK_RUNNING}} before attempting to kill the task.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
