AutopilotTestCase.launch_test_application doesn't allow to pass on custom dbus bus name.
Bug #1206011 reported by
Christopher Lee
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Autopilot |
Fix Released
|
Undecided
|
Christopher Lee | ||
autopilot (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Using AutopilotTestCa
Related branches
lp:~veebers/autopilot/fix_1206011_launch_test_app_dbus_bus
- PS Jenkins bot: Approve (continuous-integration)
- Thomi Richards (community): Approve
-
Diff: 107 lines (+59/-3)3 files modifiedautopilot/introspection/__init__.py (+7/-2)
autopilot/testcase.py (+10/-1)
autopilot/tests/functional/test_dbus_query.py (+42/-0)
Changed in autopilot: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
I ran into this issue when I was trying to run some tests using a new dbus for each test (i.e. so notifications don't interfere with the system ones). BUS_ADDRESS that it had used which by the time of the 2nd test had be closed and non-existent.
I observed that the python dbus library cached the bus (i.e. session_bus), but when closing that explicitly it used the first DBUS_SESSION_