touch-packages team mailing list archive

[Timo Jyrinki <timo.jyrinki@xxxxxxxxxxxxx>]

I've reflashed the device so this is with vivid #150 + 018. The MP in
#23 (just adjusted for AP 1.5 branch) is now in the 018 PPA.

The simplified test case seems fixed for me too, but unfortunately it'd
look like running a whole suite like phablet-test-run ubuntuuitoolkit
simply hangs at some point - in the sense that test app loads but
nothing further happens. Killing the process gets the tests to continue.
This ended up with:
http://people.canonical.com/~tjyrinki/qt5/fail/qtbase_ubuntu5/ap-
2015_03_26-09_54_27-ubuntuuitoolkit-1-018.tests - potentially less
failures (6) than before AP update, but more than before qtbase update.

The second UITK run with qtbase + AP seemingly went uninterrupted
further, but still with more (7) AP failures compared to before updating
qtbase. However, at the end of the run it seemed like the test app was
hanging - I tried gdb attaching to it, realized I didn't have debug
symbols and detached. After this it seemed the it continued and the
testing completed immediately:
http://people.canonical.com/~tjyrinki/qt5/fail/qtbase_ubuntu5/ap-
2015_03_26-09_54_27-ubuntuuitoolkit-2-018.tests

So it'd seem the AP patch does change behavior and fixes the simple
testcase, but is not the real fix. Or it's possible it fixes the AP end
but there is some sort hanging issue with the updated Qt.

-- 
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.

  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