[ https://issues.apache.org/jira/browse/MESOS-1534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vinod Kone resolved MESOS-1534. ------------------------------- Resolution: Fixed Fix Version/s: 0.20.0 commit 6f32d9a17f1a08d8d85caca5177fc4c43d6839db Author: Vinod Kone <vinodk...@gmail.com> Date: Tue Jun 24 11:22:30 2014 -0700 Explicitly terminated scheduler process in ~MesosSchedulerDriver(). Without this fix, Mesos tests that have assert failures get deadlocked on ~MesosSchedulerDriver() (because driver.stop() is not called) waiting forever for the scheduler process to exit. This causes the tests to never exit. Review: https://reviews.apache.org/r/22923 > MesosTests with assertion failure run forever > --------------------------------------------- > > 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)