unity8 unlocker code fails sometimes

[Paul Larson]

This is what we see sometimes in our CI runs:
I: Unlock failed, script output: 'The ubuntuuitoolkit.emulators module is deprecated. Import the autopilot helpers from the top-level ubuntuuitoolkit module.
INFO:unity8.process_helpers:b'unity8 stop/waiting\n'
INFO:unity8.process_helpers:unity8 start/running, process 2834

ERROR:dbus.proxies:Introspect error on :1.59:/com/canonical/Autopilot/Introspection: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/usr/lib/python3/dist-packages/unity8/process_helpers.py", line 63, in unlock_unity
    unity = _get_unity_proxy_object(pid)
  File "/usr/lib/python3/dist-packages/unity8/process_helpers.py", line 184, in _get_unity_proxy_object
    emulator_base=emulators.UnityEmulatorBase,
  File "/usr/lib/python3/dist-packages/autopilot/introspection/_search.py", line 182, in get_proxy_object_for_existing_process
    emulator_base
  File "/usr/lib/python3/dist-packages/autopilot/introspection/_search.py", line 403, in _make_proxy_object
    intro_xml = _get_introspection_xml_from_backend(dbus_address)
  File "/usr/lib/python3/dist-packages/autopilot/introspection/_search.py", line 497, in _get_introspection_xml_from_backend
    return backend.dbus_introspection_iface.Introspect()
  File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 70, in __call__
    return self._proxy_method(*args, **keywords)
  File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 145, in __call__
    **keywords)
  File "/usr/lib/python3/dist-packages/dbus/connection.py", line 651, in call_blocking
    message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

Is there some way to get the unlocker to retry this, or at least give better information about what's going on?

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Christopher Lee (veebers)]

Hi,

This bug is affecting the gatekeeper testing for releasing libautopilot-qt[1] and holding up any possible release of this code. (and will affect any other up coming test runs too).

This is a test run without the testing silo so it's not the new libautopilot-qt causing the crash.
[1] http://q-jenkins.ubuntu-ci:8080/job/autopilot-release-gatekeeper/177

But we also see it happen with the code under test, so it's hard to tell if crash is related to this existing bug or perhaps another bug introduced by the code under test (hence the hold up in testing + release).
[2] http://q-jenkins.ubuntu-ci:8080/job/autopilot-release-gatekeeper/178

[Christopher Lee (veebers)]

This crash file was taken from the gatekeeper run[1]. Note this run does include the silo ppa with the code under test but I didn't see any mention of libautopilot-qt in it so thought it would be of interest.

The crash happens at the start of the 'testing sudoku_app' log.
[1]http://q-jenkins.ubuntu-ci:8080/job/autopilot-release-gatekeeper/180/label=gatekeeper-mako/consoleText

[Michał Sawicz (saviq)]

The crash file is unfortunately uninteresting, doesn't contain the abort message, we'd need unity8.log from ~/.cache/upstart/, too.

I'll try and reproduce the issue locally.

[Michael Terry (mterry)]

I think this is caused by bug 1347789

[kevin gunn (kgunn72)]

seems right, dup of
https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1335481