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 protected]> Wed, 30 Jul 2014
16:12:30 +0000
** Changed in: dbus-cpp (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to dbus-cpp in Ubuntu.
https://bugs.launchpad.net/bugs/1326200
Title:
core::dbus::Fixture leaves stale dbus-daemon processes around if test
suite terminates
Status in DBus C++:
In Progress
Status in “dbus-cpp” package in Ubuntu:
Fix Released
Bug description:
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/dbus-cpp/+bug/1326200/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
