touch-packages team mailing list archive

[Timo Jyrinki <timo.jyrinki@xxxxxxxxxxxxx>]

I ran some Autopilot testing last night and continuing a bit now . The
two new patches do not fix the AP problems. As examples:

- Archive image (#145):
* UITK: 1-2 AP failures
* webbrowser-app: 1-2 AP failures
* calculator: 0 AP failures
* ubuntu-system-settings: 0 AP failures

- Image (#147) added with silo 018 (qtbase DBus patches)
* UITK: 7-8 failures (similar to earlier #145 + previous qtbase DBus fix build)
* webbrowser-app: 5-7 failures
* calculator: 2 failures
* ubuntu-system-settings: 16 AP failures (only 1 run done)

Details at
http://people.canonical.com/~tjyrinki/qt5/fail/qtbase_ubuntu5/

Even if the qtbase patches themselves would be correct and functioning
well and they just happen to make Autopilot break, we can't let
Autopilot regress so badly. Either there should be something more done
to Qt or an Autopilot landing fixing the issues should be put to the
same silo.

As for libusermetrics, the diff for its landing in #106 is at
http://launchpadlibrarian.net/198152771/libusermetrics_1.1.1%2B14.10.20141020-0ubuntu1_1.1.1%2B15.04.20150219-0ubuntu1.diff.gz

** Changed in: autopilot (Ubuntu)
       Status: Incomplete => New

** Changed in: qtbase-opensource-src (Ubuntu)
       Status: In Progress => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libusermetrics 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.

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