Hangs to build on ppc64el
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
content-hub (Ubuntu) |
Invalid
|
Critical
|
Unassigned |
Bug Description
It seems impossible to get ppc64el build to finish on yakkety. The build seems to fail but hangs forever (until cancelling the build job) probably because there's a test related thread loose and not killed.
--
gdk_pixbuf-2.0 -lapparmor -Wl,-rpath,
make[3]: Leaving directory '/<<BUILDDIR>
[100%] Built target content-hub-send
make[2]: Leaving directory '/<<BUILDDIR>
/usr/bin/cmake -E cmake_progress_
make[1]: Leaving directory '/<<BUILDDIR>
debian/rules override_
make[1]: Entering directory '/<<BUILDDIR>
dbus-test-runner -t make -p "-C" -p "build/
DBus daemon: unix:abstract=
task-0: Started with PID: 11044
task-0: make[2]: Entering directory '/<<BUILDDIR>
task-0: Running tests...
task-0: /usr/bin/ctest --force-
task-0: Test project /<<BUILDDIR>
task-0: Start 1: app_hub_
task-0: 1/10 Test #1: app_hub_
task-0: Start 2: app_hub_
task-0: 2/10 Test #2: app_hub_
task-0: Start 3: app_hub_
** (dbus-test-
(dbus-test-
task-0: Shutting down
DBus daemon: Shutdown
debian/rules:15: recipe for target 'override_
make[1]: *** [override_
make[1]: Leaving directory '/<<BUILDDIR>
debian/rules:7: recipe for target 'build-arch' failed
make: *** [build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2
--
This happens despite 5+ retries. Also i386 and armhf needed a retry but they did eventually finish.
This prevents getting any content-hub landing to yakkety properly.
description: | updated |
I've been experiencing this on the PPA builders for more than just content-hub. I've seen it with qtmir as well. I think there's a bigger issue with the builders.