The failure happens in both yakkity and xenial (because both use Qt
5.6). The failure moves around. In the latest build, we got a failure on
xenial ppc64el (which is a first).

If we disable tests, we have to disable *all* integration tests that use
DBus for *both* xenial and yakkety. We haven't seen a failure on vivid
so far, and I don't expect that we will, seeing that vivid uses an
earlier version of Qt.

I'm uncomfortable about turning off tests wholesale like this though. In
particular, we have a lurking time bomb here. Absolutely anything that
uses QDBus with Qt 5.6 can blow up without warning. I'm fairly sure that
this is a race condition that shows up mainly because the timings when
we run on the build machines are different. So, we may end up with tons
of seemingly random failures in the field for anything that uses QDBus,
just because a machine is more heavily loaded than usual. Random
segfaults are very hard to debug if they are not reproducible :-(

Is there any chance of backing out of the Qt 5.6 upgrade? It doesn't
look like that version is ready for prime time yet.

You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to thumbnailer in Ubuntu.

  [MIR] thumbnailer

Status in thumbnailer package in Ubuntu:

Bug description:
   * Available in universe

   * This package is required by many Ubuntu Touch applications and scopes, 
such as gallery app, music app, today scope, music scope, etc.

   * No known security issues at this time. It has been reviewed by security in 
the past for use on the phone.

  [Quality assurance]
   * This package has unit tests.

   Most dependencies are already in main with the exception of the following:
   * libboost-filesystem-dev
   * libunity-api-dev (Bug #1613563)
   * persistent-cache-cpp-dev (Bug #1613560)

   Note that the package has other dependencies that are not in main,
  but these are used only for the tests and are not runtime

  [Standards compliance]
   * This package uses cmake.

   * This package is maintained by Canonical and actively in use on the phone 

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to