Failing AP tests with trunk ui-toolkit on top of image #11

Archive version is r792 from 11 Oct? We are now at r819 so unfortunately there are a lot of changes inbetween that can be related to the issues.

I followed the steps above with image #100 on maguro, and all tests passed. Now installing the trusty-proposed image to test with that.

12 failures on maguro here http://paste.ubuntu.com/6364587/

I followed the recipe above on maguro and the 3 tests above pass (although there are some warnings):

tim@ideapad:~$ phablet-test-run ubuntuuitoolkit.tests.test_emulators.TabsTestCase.test_switch_to_previous_tab_not_from_first
adbd is already running as root
bash: cd: /home/phablet/autopilot: No such file or directory
Loading tests from: /usr/lib/python2.7/dist-packages

Tests running...
sh: 1: gcc: not found
dpkg-architecture: warning: Couldn't determine gcc system type, falling back to default (native compilation)

Ran 1 test in 8.651s
OK
tim@ideapad:~$ phablet-test-run ubuntuuitoolkit.tests.test_emulators.TabsTestCase.test_switch_to_next_tab_from_main_view
adbd is already running as root
bash: cd: /home/phablet/autopilot: No such file or directory
Loading tests from: /usr/lib/python2.7/dist-packages

Tests running...
sh: 1: gcc: not found
dpkg-architecture: warning: Couldn't determine gcc system type, falling back to default (native compilation)

Ran 1 test in 4.584s
OK
tim@ideapad:~$ phablet-test-run ubuntuuitoolkit.tests.test_emulators.TabsTestCase.test_switch_to_next_tab_from_main_view
adbd is already running as root
bash: cd: /home/phablet/autopilot: No such file or directory
Loading tests from: /usr/lib/python2.7/dist-packages

Tests running...
sh: 1: gcc: not found
dpkg-architecture: warning: Couldn't determine gcc system type, falling back to default (native compilation)

Ran 1 test in 4.826s
OK

So just to update in comments as well, removing the click autopilot tests got me passing AP:s again, but my problems do not explain the problems seen on maguro so the bug is best left open until those have been resolved.

robru is testing both uitk and apps against it now, to evaluate publishing of uitk.

I also executed phablet-test-run ubuntuuitoolkit with these results:

Ran 93 tests in 452.983s
OK

^above tests passed with

root@ubuntu-phablet:/# apt-cache policy qtdeclarative5-ubuntu-ui-toolkit-plugin
qtdeclarative5-ubuntu-ui-toolkit-plugin:
  Installed: 0.1.46+14.04.20131105.1-0ubuntu1
  Candidate: 0.1.46+14.04.20131105.1-0ubuntu1
  Version table:
 *** 0.1.46+14.04.20131105.1-0ubuntu1 0
        500 http://ppa.launchpad.net/ubuntu-unity/daily-build/ubuntu/ trusty/main armhf Packages
        100 /var/lib/dpkg/status
     0.1.46+13.10.20131011.2-0ubuntu1 0
        500 http://ports.ubuntu.com/ubuntu-ports/ trusty/main armhf Packages

I got the same errors as Timo when running the tests with phablet-test-run on my mako.
All the tests pass for me when using trunk and autopilot run inside the adb shell.

It doesn't matter if I run from source or from the installed package using adb shell, it always passes.
So I get different results if running with phablet-test-run than with adb shell + autopilot run. Weird.

Leo: do you have /home/phablet/autopilot directory? If yes, try moving it away. Otherwise I don't immediately see where you'd get the difference. My problems were caused by /home/phablet/autopilot having different tests from the ubuntu-ui-toolkit-autopilot package.

Ah, you are right Timo. Scratch all my analysis.
ChrisGagnon is debugging this, he says it's because of the animation of the tabs.

Both maguro and mako seem to have UI Toolkit tests run successfully:

http://reports.qa.ubuntu.com/smokeng/trusty/touch/maguro/15:20131107.1:20131031.1/4937/
http://reports.qa.ubuntu.com/smokeng/trusty/touch/mako/15:20131107.1:20131031.1/4936/

Christian, feel free to reopen if there's something still to do about those 12 failing tests on maguro you encountered.