Public bug reported:
The builds for riscv64 on e.g.
https://launchpad.net/ubuntu/+source/dee/1.2.7+17.10.20170616-6build1
hang eventually.
All other architectures work fine.
Build log tail will be like:
...
symlinking changelog.Debian.gz in dee-tools to file in libdee-1.0-4
pkgstripfiles: Running PNG optimization (using 8 cpus) for package dee-tools ...
pkgstripfiles: No PNG files.
dpkg-deb: building package 'dee-tools' in
'../dee-tools_1.2.7+17.10.20170616-6build1_riscv64.deb'.
pkgstriptranslations: libdee-1.0-4-dbgsym does not contain translations,
skipping
pkgstriptranslations: no translation files, not creating tarball
pkgmaintainermangler: Not overriding Maintainer for domain lists.ubuntu.com
pkgstripfiles: processing control file:
debian/.debhelper/libdee-1.0-4/dbgsym-root/DEBIAN/control, package
libdee-1.0-4-dbgsym, directory debian/.debhelper/libdee-1.0-4/dbgsym-root
dpkg-deb: building package 'libdee-1.0-4-dbgsym' in
'debian/.debhelper/scratch-space/build-libdee-1.0-4/libdee-1.0-4-dbgsym_1.2.7+17.10.20170616-6build1_riscv64.deb'.
Renaming libdee-1.0-4-dbgsym_1.2.7+17.10.20170616-6build1_riscv64.deb to
libdee-1.0-4-dbgsym_1.2.7+17.10.20170616-6build1_riscv64.ddeb
pkgstriptranslations: dee-tools-dbgsym does not contain translations, skipping
pkgstriptranslations: no translation files, not creating tarball
pkgmaintainermangler: Not overriding Maintainer for domain lists.ubuntu.com
pkgstripfiles: processing control file:
debian/.debhelper/dee-tools/dbgsym-root/DEBIAN/control, package
dee-tools-dbgsym, directory debian/.debhelper/dee-tools/dbgsym-root
dpkg-deb: building package 'dee-tools-dbgsym' in
'debian/.debhelper/scratch-space/build-dee-tools/dee-tools-dbgsym_1.2.7+17.10.20170616-6build1_riscv64.deb'.
Renaming dee-tools-dbgsym_1.2.7+17.10.20170616-6build1_riscv64.deb to
dee-tools-dbgsym_1.2.7+17.10.20170616-6build1_riscv64.ddeb
dpkg-genbuildinfo --build=any
dpkg-genchanges --build=any -mLaunchpad Build Daemon
<buildd@riscv64-qemu-lcy01-015.buildd>
>../dee_1.2.7+17.10.20170616-6build1_riscv64.changes
dpkg-genchanges: info: binary-only arch-specific upload (source code and
arch-indep packages not included)
dpkg-source --after-build .
dpkg-buildpackage: info: binary-only upload (no source included)
Then it will be stuck until at 24h a timeout will reap the builder.
It turned out (thanks cjwatson) that on these systems there is a
leftover process
Zombie schroot process
Looks like there's a dbus-daemon process still running in the background of the
build that the build didn't clean up properly
buildd 481987 0.0 0.0 5244 2780 ? S Aug10 0:00 dbus-daemon
--config-file /usr/share/dbus-test-runner/session.conf --print-address
# ls -l /proc/481987/cwd
lrwxrwxrwx 1 buildd buildd 0 Aug 11 10:08 /proc/481987/cwd ->
/home/buildd/build-PACKAGEBUILD-19646792/chroot-autobuild/build/dee-1HAMJl/dee-1.2.7+17.10.20170616/tests
On #ubuntu-devel we discussed this and agreed that we should not just retry
until it slips through by accident, we might never be able to build it again.
Instead we should try looking for what actually hangs on riscv64 and
why.
** Affects: dee (Ubuntu)
Importance: Medium
Status: Confirmed
** Tags: update-excuse
** Tags added: update-excuse
** Changed in: dee (Ubuntu)
Status: New => Confirmed
** Changed in: dee (Ubuntu)
Importance: Undecided => Medium
** Summary changed:
- riscv64 build issue hang at the end of the build (groovy)
+ riscv64 build - hang at the end of the build (groovy)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891158
Title:
riscv64 build - hang at the end of the build (groovy)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dee/+bug/1891158/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
