-
Type: Bug
-
Resolution: Done
-
Priority: Blocker - P1
-
Affects Version/s: None
-
Component/s: None
See the abrupt time jump here: https://mci.10gen.com/task_log_raw/mongodb_cpp_driver_windows_64_msvc2010_dbg_dyn_dyn_2d738d6a1064920151f380513363027228258caf_15_01_23_23_38_04_integration_test_latest_windows_64_msvc2010_dbg_dyn_dyn/0?type=T#L843
Seems to be related to a failed attempt to shut down MO.
I have a patch here: (https://mci.10gen.com/version/54c666ab3ff122791300036a_0) that just relies on the killall_mci expansion to pwn MO, since it kills all python processes and any mongo(s|d) that MO may have started. However, I think I want to investigate a bit more on a spawnhost first as giving up on clean shutdown is a bit hacky.