core::dbus::Fixture leaves stale dbus-daemon processes around if test suite terminates

[James Henstridge]

If a test suite terminates without core::dbus::Fixture's destructor running, two stale dbus-daemon subprocesses are left running. Among other things, this can lead to apparent test suite hangs when running under cmake/ctest: ctest doesn't consider a test to have completed until stdout/stderr are closed, and the dbus-daemon subprocesses hold those file descriptors open. The default timeout for tests seems to be 2 hours, so this can introduce a long delay.

It is clear that cases where this happens are errors, but as this class is intended to be used in test suites, it would be nice if it was a bit more robust about making sure the subprocesses are cleaned up.

[Launchpad Janitor (janitor)]

This bug was fixed in the package dbus-cpp - 4.0.0+14.10.20140730-0ubuntu1

---------------
dbus-cpp (4.0.0+14.10.20140730-0ubuntu1) utopic; urgency=low

  [ Ubuntu daily release ]
  * debian/libdbus-cpp4.symbols.32bit: auto-update to released version
  * debian/libdbus-cpp4.symbols.64bit: auto-update to released version

  [ thomas-voss ]
  * Make sure that dbus daemon instances fired up for testing are torn
    down after a configurable timeout. (LP: #1326200)
  * Make sure that core::dbus::Service::Service(...) interprets return
    values of dbus_bus_request_name correctly. (LP: #1329211)
 -- Ubuntu daily release <email address hidden> Wed, 30 Jul 2014 16:12:30 +0000