touch-packages team mailing list archive

[Timo Jyrinki <timo.jyrinki@xxxxxxxxxxxxx>]

The earlier simplified test case does not fail anymore or at least not
easily. Whether on stock image or using the PPA, the problem with
running the same test over and over is that Unity8 crashes or restarts
sooner or later when running the command, for example that crasher bug
noticed.

I ran a new baseline set of results on Saturday with image #153 to see
how the situation looks like on mako after the Mir, UITK, glibc
landings. It's still the same - UITK, webbrowser, calculator, ubuntu-
system-settings, ubuntu-weather-app are good examples of suites that
100% pass on stock image. They gain respectively 4/9, 3/6, 1/1, 4/7, 3/4
tests failing based on two autopilot runs with the PPA 018 in use. The
failures are random, ie the test failing changes depending on the run.

In other words, to reproduce the autopilot problem when using the PPA you can run any of the following on mako:
phablet-test-run ubuntuuitoolkit
phablet-test-run webbrowser_app
phablet-test-run ubuntu_calculator_app
phablet-test-run ubuntu_system_settings
phablet-test-run ubuntu_weather_app

Prepare the device by first running on device sudo apt install ubuntu-
ui-toolkit-autopilot webbrowser-app-autopilot ubuntu-system-settings-
autopilot python3-lxml

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to autopilot in Ubuntu.
https://bugs.launchpad.net/bugs/1421009

Title:
  unity8 sometimes hangs on boot

Status in autopilot package in Ubuntu:
  New
Status in libusermetrics package in Ubuntu:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  The following gdbus call is failing with a "Error: Timeout was
  reached" message:

  gdbus call --session --dest com.canonical.UnityGreeter --object-path /
  --method org.freedesktop.DBus.Properties.Get
  com.canonical.UnityGreeter IsActive

  This is being seen on krillin devices starting with image 106 from
  ubuntu-touch/devel-proposed. It doesn't happen every time, so far
  today, I've seen it 3 times from about 12 tests. On the most recent
  failure, I grabbed a console and tried repeatedly to run the command
  from the shell, even after 2 hours the timeout was still being
  returned (after about 28 seconds).

  A copy of ~/.cache/upstart/unity8.log is here:
  http://paste.ubuntu.com/10179482/

  I have 3 test cases where the problem was observed:
  http://d-jenkins.ubuntu-ci:8080/job/vivid-boottest-qtchooser/1/console
  http://d-jenkins.ubuntu-ci:8080/job/vivid-boottest-gsettings-ubuntu-touch-schemas/1/console
  http://d-jenkins.ubuntu-ci:8080/job/fjg-boottest/3/console

  In all cases, the test is using adt-run (from autopkgtest) to drive a
  test on the phone device. adt-run uses the above gdbus call to
  determine if the desktop is active. In all the examples, the device
  was freshly flashed.

  Update 2015-03-25: the qtbase dbus update in silo 018 seems to address
  the boot issue, but causes autopilot to have problems seeing an
  application start, randomly

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autopilot/+bug/1421009/+subscriptions