bamf tests need to cleanup dbus resources
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
BAMF |
Fix Released
|
High
|
Marco Trevisan (Treviño) | ||
0.4 |
Fix Committed
|
High
|
Marco Trevisan (Treviño) | ||
bamf (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Raring |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[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
...
Related branches
- PS Jenkins bot (community): Approve (continuous-integration)
- Francis Ginther: Approve
-
Diff: 15 lines (+5/-1)1 file modifiedtests/Makefile.am.gtests (+5/-1)
- Francis Ginther: Approve
- PS Jenkins bot (community): Approve (continuous-integration)
-
Diff: 15 lines (+5/-1)1 file modifiedtests/Makefile.am.gtests (+5/-1)
Changed in bamf: | |
assignee: | nobody → Marco Trevisan (Treviño) (3v1n0) |
Changed in bamf: | |
status: | New → In Progress |
milestone: | none → 0.5.0 |
description: | updated |
tags: |
added: verification-done removed: verification-needed |
Fix committed into lp:bamf at revision 542, scheduled for release in bamf, milestone 0.5.0