ubuntuuitoolkit tests hang on touch_custom suite

It's a bit difficult to reproduce this locally for me, but it happens 100% of the time ont he dashboard. To try to reproduce:

ubuntu-device-flash --channel devel-proposed-customized
phablet-click-test-setup

adb shell mount -o rw,remount /
adb shell apt-get install ubuntu-ui-toolkit-autopilot

phablet-test-run ubuntuuitoolkit

This image contains a customized theme, which can be found in /custom/xdg/data/themes/Ubuntu/Custom

I've reproduced this locally, and it's important to note that the phone is still responsive, it's just the test that seems to be hanging.

Plenty of the tests are showing up only white screen. This happens when the component cannot load the visuals. Either the theme is broken, or the theme engine has bugs. I will check the toolkit gallery, whether that works or not.

Hmm... I do not see XDG_DATA_DIRS set...

I grabbed the theme from the phone and set up the environment to use the theme same way the phone does. I copied the theme files under my home folder into custom-theme path, so ~/custom-theme/themes/Ubuntu/Custom was the path to the files. $HOME/.config/ubuntu-ui-toolkit/theme.ini has the theme=themes.Ubuntu.Custom line set.

Environment: XDG_DATA_DIRS=$XDG_DATA_DIRS:$HOME/custom-theme

Running ubuntu-ui-toolkit-gallery example on the desktop, I'm getting the following warning just by launching it:
(file:///home/zsombor/custom-themes/themes/Ubuntu/Custom/MainViewStyle.qml:45, unknown) - file:///home/zsombor/custom-themes/themes/Ubuntu/Custom/MainViewStyle.qml:45:5: QML QQuickImage: Cannot open: file:///home/zsombor/custom-themes/themes/Ubuntu/Custom/artwork/background_paper.png
(file:///home/zsombor/custom-themes/themes/Ubuntu/Custom/MainViewStyle.qml:42, unknown) - file:///home/zsombor/custom-themes/themes/Ubuntu/Custom/MainViewStyle.qml:42: ReferenceError: internals is not defined
(file:///home/zsombor/custom-themes/themes/Ubuntu/Custom/MainViewStyle.qml:42, unknown) - file:///home/zsombor/custom-themes/themes/Ubuntu/Custom/MainViewStyle.qml:42: ReferenceError: internals is not defined

Never the less these are only errors on MainViewStyle, these should be all corrected. Otherwise the application works smoothly, all the colours are taken from the custom theme, so the theme seems to be loaded fine. However, if I run autopilot tests with the theme, all of them seem to be broken, like the environment variables would have not been loaded in the tests.

Where can I see the theme being used here?

The autopilot test shouldn't pick up custom themes, we only check the default theme and ultimately things like color checks will fail even if your theme is bug-free.

I disagree that it shouldn't pick up custom themes. This is a fundamental
part of the customized image, and needs to be tested. The theme can be
found in lp:savilerow, and is quite literally just a different color Palette

On Thu, Apr 17, 2014 at 8:23 AM, Christian Dywan <email address hidden>wrote:

> Where can I see the theme being used here?
>
> The autopilot test shouldn't pick up custom themes, we only check the
> default theme and ultimately things like color checks will fail even if
> your theme is bug-free.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1297846
>
> Title:
> ubuntuuitoolkit tests hang on touch_custom suite
>
> Status in The Savilerow project:
> Confirmed
> Status in Ubuntu UI Toolkit:
> Confirmed
> Status in “ubuntu-ui-toolkit” package in Ubuntu:
> New
>
> Bug description:
> The ubuntuuitoolkit tests fail reliably, as they get caught repeating
> this:
>
> 08:41:19.917 DEBUG dbus:432 - Selecting objects of any type with
> attributes: {'objectName': 'testListElement5'}
> 08:41:20.524 INFO logging:45 - QQuickListView:
> _show_more_elements_below. Arguments (). Keyword arguments: {}.
> 08:41:20.615 DEBUG _uinput:546 - Dragging from 432,413 to 432,100
> 08:41:21.343 DEBUG dbus:432 - Selecting objects of any type with
> attributes: {'objectName': 'testListElement5'}
> 08:41:21.868 INFO logging:45 - QQuickListView:
> _show_more_elements_below. Arguments (). Keyword arguments: {}.
> 08:41:21.962 DEBUG _uinput:546 - Dragging from 432,413 to 432,100
> 08:41:22.757 DEBUG dbus:432 - Selecting objects of any type with
> attributes: {'objectName': 'testListElement5'}
> 08:41:23.302 INFO logging:45 - QQuickListView:
> _show_more_elements_below. Arguments (). Keyword arguments: {}.
> 08:41:23.450 DEBUG _uinput:546 - Dragging from 432,413 to 432,100
> 08:41:24.260 DEBUG dbus:432 - Selecting objects of any type with
> attributes: {'objectName': 'testListElement5'}
> 08:41:24.753 INFO logging:45 - QQuickListView:
> _show_more_elements_below. Arguments (). Keyword arguments: {}.
> 08:41:24.832 DEBUG _uinput:546 - Dragging from 432,413 to 432,100
> 08:41:25.622 DEBUG dbus:432 - Selecting objects of any type with
> attributes: {'objectName': 'testListElement5'}
> 08:41:26.236 INFO logging:45 - QQuickListView:
> _show_more_elements_below. Arguments (). Keyword arguments: {}.
> 08:41:26.333 DEBUG _uinput:546 - Dragging from 432,413 to 432,100
> 08:41:27.104 DEBUG dbus:432 - Selecting objects of any type with
> attributes: {'objectName': 'testListElement5'}
> 08:41:27.666 INFO logging:45 - QQuickListView:
> _show_more_elements_below. Arguments (). Keyword arguments: {}.
> 08:41:27.745 DEBUG _uinput:546 - Dragging from 432,413 to 432,100
> 08:41:28.508 DEBUG dbus:432 - Selecting objects of any type with
> attributes: {'objectName': 'testListElement5'}
> 08:41:29.043 INFO logging:45 - QQuickListView:
> _show_more_elements_below. Arguments (). Keyword arguments: {}.
> 08:41:29.238 DEBUG _uinput:546 - Dragging from 432,413 to 432,100
>
> for about 5 hours until some timeout is reached.
>
> Test results are t...

anyone still think we need to keep this bug since no traffic for half of a year ?