[ https://issues.apache.org/jira/browse/MESOS-1534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vinod Kone updated MESOS-1534: ------------------------------ Summary: Scheduler process is not explicitly terminated in the destructor of MesosSchedulerDriver. (was: MesosTests with assertion failure run forever) > Scheduler process is not explicitly terminated in the destructor of > MesosSchedulerDriver. > ----------------------------------------------------------------------------------------- > > Key: MESOS-1534 > URL: https://issues.apache.org/jira/browse/MESOS-1534 > Project: Mesos > Issue Type: Bug > Reporter: Vinod Kone > Assignee: Vinod Kone > Fix For: 0.20.0 > > > When a Mesos test fails due to an assertion error driver.stop() is not called > but ~MesosSchedulerDriver() might be called (if it's on the stack). The > destructor will block on the scheduler process termination which never > happens because driver.stop() is not called. -- This message was sent by Atlassian JIRA (v6.2#6252)