Merge lp:~thomir-deactivatedaccount/autopilot-qt/always-send-dbus-reply into lp:autopilot-qt
Status: | Merged |
---|---|
Approved by: | Michael Zanetti |
Approved revision: | 40 |
Merged at revision: | 41 |
Proposed branch: | lp:~thomir-deactivatedaccount/autopilot-qt/always-send-dbus-reply |
Merge into: | lp:autopilot-qt |
Diff against target: |
126 lines (+47/-38) 1 file modified
driver/dbus_object.cpp (+47/-38) |
To merge this branch: | bzr merge lp:~thomir-deactivatedaccount/autopilot-qt/always-send-dbus-reply |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
PS Jenkins bot | continuous-integration | Approve | |
Christopher Lee (community) | Approve | ||
Review via email: mp+153471@code.launchpad.net |
Commit message
Autopilot-qt now sends empty dbus replies when a call fails, instead of not sending a reply at all.
Description of the change
Problem:
Sometimes, autopilot-qt fails to find the node specified by autopilot client side. This most often happens when the node is removed, or when xpathsleect fails for some reason. When this happens, autopilot-qt fails to send a dbus reply message, which makes whatever is on the client side hang for the dbus timeout period (10 seconds, I think).
Solution:
This branch makes autopilot-qt send an empty dbus reply straight away. This avoids the timeout on the client-side.
Tested interactively. To reproduce, run autopilot vis against an application running autopilot-qt without this branch - you will see a long delay whenever selecting an object. Running it against autopilot-qt that's built from this branch will remove that delay.
FAILED: Autolanding. jenkins. qa.ubuntu. com/job/ autopilot- qt-autolanding/ 1/ jenkins. qa.ubuntu. com/job/ autopilot- qt-raring- amd64-autolandi ng/1/console jenkins. qa.ubuntu. com/job/ autopilot- qt-raring- armhf-autolandi ng/1/console
More details in the following jenkins job:
http://
Executed test runs:
SUCCESS: http://
FAILURE: http://