** Changed in: thumbnailer (Ubuntu)
Status: Incomplete => Fix Released
--
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
Looks like 1991 has landed 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:
The package in the archive still depends on boost1.60, so this can't be
promoted until ticket #1991 lands in the archive.
--
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]
Tests are disabled for on arm64, ppc64, and ppc64le for yakkety and
xenial. That's where we've seen failures, and we don't particularly care
about these arches at the moment.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Changes are in silo 1991.
--
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:
FWIW, I'm seeing very similar issues on indicator-network. It too uses
qdbus, and I'm seeing a high volume of test regressions on yakkety arm64
and ppc64el: https://bugs.launchpad.net/ubuntu/+source/indicator-
network/+bug/1626767
--
You received this bug notification because you are a member of
OK, will do that on Monday.
--
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:
I'd go for disabling yakkety arm64 and ppc64el, to disable the minimum
required. This is usually the case that's wanted. That way we'd catch
any further regressions while Ubuntu keeps on changing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Hmmm... The xenial failure is highly suspicious because that particular
test has never failed before. I'm quite confident that the failure
exists on xenial too, just doesn't manifest as often.
I did look at the telepathy code changes, and they address a completely
different issue. What we are
I think disabling the tests on xenial is a bad idea since they seem to
pass most of the time (every time I tried), while they never pass on
yakkety. Since xenial + Qt 5.6 is the next stable platform and the tests
pass there (possibly with some flakiness still), there's value to keep
them enabled.
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
Oh, no I did earlier in comment #1. :P
OK, if you can whip up a targeted test-disabling with comment why, this
should be fine.
--
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]
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
I decided to kick the build in silo 1968 to see whether the fault would
move. This time, it failed on yakkety on arm64 and ppc64el as before,
but also failed on xenial powerpc. The failure on xenial is in a test
that uses QDBus to talk between client and server. The client fails
because it doesn't
Another option: it could simply a race that shows up in the train only
because the builders are VMs (I believe) and the underlying hardware
might be loaded more heavily. I'd expect CPU and I/O timings to be
different in the train than on my M10. So, it is still possible that
this is simply a race
I install a yakkety arm64 chroot on my M10 and built the thumbnailer.
The tests run fine, over and over. I do not see any failures.
dpkg reports:
libc6:arm64 2.24-0ubuntu1
arm64
gcc-66.2.0-3ubuntu15
It does not seem to help building with those two additional QDBus
patches (qtbase 5.6.1+dfsg-3ubuntu6~1):
https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/1968/+build/10936648/+files/buildlog_ubuntu-
yakkety-ppc64el.thumbnailer_2.4+16.10.20160921-0ubuntu1_BUILDING.txt.gz
Another full
Silo 1968 contains a no-change rebuild of the thumbnailer. As expected,
things are again blowing up for arm64 and ppc64el on yakkety.
Interestingly, things worked with xenial, even though the same QDBus is
installed there, as far as I can see.
I don't think the telepathy code changes you linked
Since this is a MIR bug I've filed bug #1625930 separately.
--
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:
Ok I've now finished a rebuild and realized it would not have raised any
flags for me earlier since my test silo only early built only for amd64,
armhf and i386. I've now added arm64 to the mix.
This QDBus problem seems more architecture specific than the others
were.
** Also affects:
And I'm sorry, I did do rebuilds of 38 other Qt using packages in our
phone stack in July/August in order to file bugs (like the signon and
telepathy-qt ones), but it seems thumbnailer was indeed not in my
package list before this.
--
You received this bug notification because you are a member
For the record, the so far included post-5.6.1 patches in our packages:
https://codereview.qt-project.org/#/c/167480/
https://codereview.qt-project.org/#/c/170356/
Thiago is the main contact in upstream.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
As with unity-scope-click, you could try out https://requests.ci-
train.ubuntu.com/#/ticket/1960 which has two pending QDBus patches that
are however not yet merged or approved in upstream.
We had also problems with telepathy-qt and signon with QDBus, but two
patches were landed that made QDBus
So, as best as we can tell, this is caused by an upgrade to Qt.
Specifically, anything that uses QDBus is falling over. We are seeing
similar problems with unity-scope-click here:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-
src/+bug/1618590
Basically, the code works with Qt 5.5,
The tests that are failing are all Qt related. I suspect a problem in Qt
rather than our code. (The thumbnailer code hasn't changed in ages, and
the fact that it fails only on Yakkity suggest a problem with one of our
dependencies.)
8: thumbnailer-service: [23:19:59.671] failure cache: 0
still ftbfs on arm64 and ppc64el, where it built before:
https://launchpad.net/ubuntu/+source/thumbnailer/2.4+16.10.20160825-0ubuntu1
--
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:
I didn't even know that there was a failed build. Looking at the build
log, the test failures are almost certainly caused by a flaky builder.
We have seen this sort of thing recently on another project too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
according to
http://people.canonical.com/~ubuntu-archive/transitions/html/html/boost1.61.html
it's not yet fixed in the archive.
--
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]
Well, it's not ftbfs anymore. More pertinently, should I publish now or
wait until after OTA-13?
--
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
will stay as incomplete until the ftbfs is fixed.
--
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:
Silo 54 is approved for QA. I was told not to publish this until after
OTA-13. If this needs to go in now, someone let me know please, and I'll
publish it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Unfortunately, silo 54 failed to build again, this time anything qt
related fell over on yakkety. Yesterday, the same silo built fine (just
didn't pass autopkg tests). I'm getting the impression that not all of
the Arm builders have the same qt version installed. It's the only
reason I can think
We are running gstreamer out of process (inside vs-thumb) because
several codecs have problems and can cause infinite loops, hangs, or
segfaults. If vs-thumb crashes, we don't want to generate a bug report
because, sadly, the crashes happen quite often.
The ftbfs is the unity8 problem, yes.
--
- Why do we install an apport blacklist for vs-thumb?
- Are the ftbfs in -proposed something we have a fix for? (Is that the silo
that is held up by a failing u8 test?)
Otherwise seems fine.
** Changed in: thumbnailer (Ubuntu)
Status: New => Incomplete
--
You received this bug
** Description changed:
[Availability]
- * Available in universe
+ * Available in universe
[Rationale]
- * This package is required by many Ubuntu Touch applications and scopes,
such as gallery app, music app, today scope, music scope, etc.
+ * This package is required by many Ubuntu
35 matches
Mail list logo
