touch-packages team mailing list archive
-
touch-packages team
-
Mailing list archive
-
Message #91302
[Bug 1476715] [NEW] Autopilot tests on desktop fail when trying to detect maliit
Public bug reported:
I am trying to run AP tests on the desktop for a webbrowser-app branch that uses components from UITK 1.3.
I build and install UITK packages from the trunk.
When running tests that use the keyboard, they all fail with the
following exception (elided for clarity):
File "/usr/lib/python3/dist-packages/ubuntuuitoolkit/_custom_proxy_objects/_common.py", line 58, in get_keyboard
if is_maliit_process_running():
File "/usr/lib/python3/dist-packages/ubuntuuitoolkit/_custom_proxy_objects/_common.py", line 193, in is_maliit_process_running
return is_process_running(MALIIT)
File "/usr/lib/python3/dist-packages/ubuntuuitoolkit/_custom_proxy_objects/_common.py", line 188, in is_process_running
return 'start/' in get_process_status(name)
File "/usr/lib/python3/dist-packages/ubuntuuitoolkit/_custom_proxy_objects/_common.py", line 177, in get_process_status
"Unable to get {}'s status: {}".format(name, error)
ubuntuuitoolkit._custom_proxy_objects._common.ToolkitException: Unable to get maliit-server's status: Command '['/sbin/initctl', 'status', 'maliit-server']' returned non-zero exit status 1
What seems to be happening is that the UITK emulators are trying to see
if maliit-server is running by asking the status of the job, but there
is no such job installed at all on desktop, so this always fails.
** Affects: ubuntu-ui-toolkit (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1476715
Title:
Autopilot tests on desktop fail when trying to detect maliit
Status in ubuntu-ui-toolkit package in Ubuntu:
New
Bug description:
I am trying to run AP tests on the desktop for a webbrowser-app branch that uses components from UITK 1.3.
I build and install UITK packages from the trunk.
When running tests that use the keyboard, they all fail with the
following exception (elided for clarity):
File "/usr/lib/python3/dist-packages/ubuntuuitoolkit/_custom_proxy_objects/_common.py", line 58, in get_keyboard
if is_maliit_process_running():
File "/usr/lib/python3/dist-packages/ubuntuuitoolkit/_custom_proxy_objects/_common.py", line 193, in is_maliit_process_running
return is_process_running(MALIIT)
File "/usr/lib/python3/dist-packages/ubuntuuitoolkit/_custom_proxy_objects/_common.py", line 188, in is_process_running
return 'start/' in get_process_status(name)
File "/usr/lib/python3/dist-packages/ubuntuuitoolkit/_custom_proxy_objects/_common.py", line 177, in get_process_status
"Unable to get {}'s status: {}".format(name, error)
ubuntuuitoolkit._custom_proxy_objects._common.ToolkitException: Unable to get maliit-server's status: Command '['/sbin/initctl', 'status', 'maliit-server']' returned non-zero exit status 1
What seems to be happening is that the UITK emulators are trying to
see if maliit-server is running by asking the status of the job, but
there is no such job installed at all on desktop, so this always
fails.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1476715/+subscriptions
Follow ups