If we do believe that the test failures are specific to Qt and thus not something this package can do something about, I'm fine with a targeted disabling of tests until we can root-cause Qt. No reason to block on something we can't yet fix.
*Ideally* we'd disable only the flaky tests, only on yakkety, and only on arm64 and ppc64el. With a comment pointing to the qt bug so we know when we can re-enable them. I'll take as much of that as I can get (i.e. if you have to disable all tests on those distro/arches instead, OK...) ppc64el wouldn't normally bother me TOO much. It's not a targeted platform for this code at the moment. But arm64 is (or shortly will be), and the failure there is worrisome. I don't see evidence that this got a packaging look through. I'll do that now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1613561 Title: [MIR] thumbnailer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thumbnailer/+bug/1613561/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
