touch-packages team mailing list archive

[Richard Huddie <richard.huddie@xxxxxxxxxxxxx>]

I tried reproducing this issue on silo 18 using
address_book_app.tests.test_add_contact.TestAddContact.test_go_to_add_contact.

The test failed on the 10th attempt in the same way as in the logs:
http://people.canonical.com/~tjyrinki/qt5/fail/qtbase_ubuntu5/ap-
2015_03_24-21_48_11-address_book_app-1-018.tests

Watching the test, the address-book-app froze as it was launching,
displaying a frozen spinner on the loading screen. Autopilot then timed
out waiting for the app to launch and reported the introspection
failure.

Subsequent tests then failed with the maliit-server error as reported in
the same logs.

The only crash file reported was: _usr_lib_telepathy_mission-
control-5.32011.crash

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