| 2012-12-10 22:45:05 |
Francis Ginther |
bug |
|
|
added bug |
| 2013-06-08 14:51:55 |
Marco Trevisan (Treviño) |
bamf: assignee |
|
Marco Trevisan (Treviño) (3v1n0) |
|
| 2013-06-08 16:16:15 |
Marco Trevisan (Treviño) |
bamf: status |
New |
In Progress |
|
| 2013-06-08 16:16:17 |
Marco Trevisan (Treviño) |
bamf: milestone |
|
0.5.0 |
|
| 2013-06-08 16:16:26 |
Marco Trevisan (Treviño) |
nominated for series |
|
bamf/0.4 |
|
| 2013-06-08 16:16:26 |
Marco Trevisan (Treviño) |
bug task added |
|
bamf/0.4 |
|
| 2013-06-08 16:16:31 |
Marco Trevisan (Treviño) |
bamf/0.4: status |
New |
In Progress |
|
| 2013-06-08 16:16:33 |
Marco Trevisan (Treviño) |
bamf/0.4: assignee |
|
Marco Trevisan (Treviño) (3v1n0) |
|
| 2013-06-08 16:16:38 |
Marco Trevisan (Treviño) |
bamf/0.4: importance |
Undecided |
High |
|
| 2013-06-08 16:16:40 |
Marco Trevisan (Treviño) |
bamf/0.4: milestone |
|
0.4.1 |
|
| 2013-06-08 16:27:01 |
Launchpad Janitor |
branch linked |
|
lp:~3v1n0/bamf/tests-dbus-cleanup-0.4 |
|
| 2013-06-08 16:29:55 |
Launchpad Janitor |
branch linked |
|
lp:~3v1n0/bamf/tests-dbus-cleanup |
|
| 2013-06-10 18:48:10 |
PS Jenkins bot |
bamf: status |
In Progress |
Fix Committed |
|
| 2013-06-10 21:28:17 |
Marco Trevisan (Treviño) |
bamf/0.4: status |
In Progress |
Fix Committed |
|
| 2013-06-19 11:37:18 |
Łukasz Zemczak |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2013-06-19 11:45:12 |
Łukasz Zemczak |
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
... |
[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
... |
|
| 2013-06-19 14:21:47 |
Launchpad Janitor |
bamf (Ubuntu): status |
New |
Fix Released |
|
| 2013-06-25 05:06:04 |
Adam Conrad |
bamf (Ubuntu Raring): status |
New |
Fix Committed |
|
| 2013-06-25 05:06:07 |
Adam Conrad |
bug |
|
|
added subscriber SRU Verification |
| 2013-06-25 05:06:15 |
Adam Conrad |
tags |
|
verification-needed |
|
| 2013-07-25 12:05:46 |
Marco Trevisan (Treviño) |
tags |
verification-needed |
verification-done |
|
| 2013-08-12 13:12:42 |
Launchpad Janitor |
bamf (Ubuntu Raring): status |
Fix Committed |
Fix Released |
|
| 2013-08-12 13:13:04 |
Scott Kitterman |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2013-08-30 17:00:42 |
Marco Trevisan (Treviño) |
bamf: status |
Fix Committed |
Fix Released |
|
