** Description changed: + [Impact] + + This fix is necessary also from the point of view of daily-release and + automerging on jenkins - otherwise jenkins was trashed with hanging + processes. + + [Test Case] + + 1. Run the headless unit tests (make test-headless) + 2. Make sure there are no leftover dbus-daemon's running afterwards + + [Regression Potential] + + Broken DBus on the test system, most unlikely. + + Original description: + The bamf integration tests do not cleanup the dbus-daemon process. This results in two process left open after every bamf build on the jenkins autolanding environment. This may be a contributing factor to some test failures as the builds tend to be more successful after cleaning up these dbus-daemon processes on the build machines. The processes look like this: # ps -ef|grep dbus-daemon 1234 13257 1 0 22:04 ? 00:00:00 //bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session 1234 13854 1 0 22:04 ? 00:00:00 //bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session ...
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1088696 Title: bamf tests need to cleanup dbus resources To manage notifications about this bug go to: https://bugs.launchpad.net/bamf/+bug/1088696/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
