python-dbusmock

DBusTestCase.spawn_server() says spawned daemon will exit when bus closes, but process is left behind

Bug #1156561 reported by James Henstridge
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
python-dbusmock
Fix Released
Medium
Unassigned

Bug Description

The docstring for DBusTestCase.spawn_server() says:

        The daemon will terminate automatically when the D-BUS that it connects
        to goes down. If that does not happen (e. g. you test on the actual
        system/session bus), you need to kill it manually.

However the daemon process appears to stick around once the test suite completes, even though the temporary bus it was connected to has shut down.

Martin Pitt (pitti)
Changed in python-dbusmock:
status: New → In Progress
assignee: nobody → Martin Pitt (pitti)
Revision history for this message
Martin Pitt (pitti) wrote :

Fixed with a test case in http://bazaar.launchpad.net/~pitti/python-dbusmock/trunk/revision/112

Changed in python-dbusmock:
assignee: Martin Pitt (pitti) → nobody
importance: Undecided → Medium
status: In Progress → Fix Committed
Revision history for this message
Martin Pitt (pitti) wrote :

Fix included in the 0.6 release which I just pushed out.

Changed in python-dbusmock:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.