Bug#863927: qtwebengine-opensource-src: FTBFS: memory exhausted
Source: qtwebengine-opensource-src
Version: 5.7.1+dfsg-6
Severity: serious
Tags: stretch sid
User: debian-qa@lists.debian.org
Usertags: qa-ftbfs-20170601-i386 qa-ftbfs
Justification: FTBFS in stretch on i386
Hi,
During a rebuild of all packages in stretch (in a stretch chroot, not a
sid chroot), your package failed to build on i386.
Note that the build node has a lot of RAM, so if memory is really
exhausted, it could mean that it can no longer be built on i386.
Relevant part (hopefully):
> make[1]: Entering directory '/<<BUILDDIR>>/qtwebengine-opensource-src-5.7.1+dfsg'
> dh_link --package=qt5webengine-examples \
> usr/share/javascript/jquery/jquery.min.js usr/lib/i386-linux-gnu/qt5/examples/webenginewidgets/contentmanipulation/jquery.min.js \
> usr/share/javascript/marked/marked.min.js usr/lib/i386-linux-gnu/qt5/examples/webenginewidgets/markdowneditor/resources/marked.min.js
> dh_link --remaining-packages
> make[1]: Leaving directory '/<<BUILDDIR>>/qtwebengine-opensource-src-5.7.1+dfsg'
> dh_strip_nondeterminism
> dh_compress
> dh_fixperms
> dh_strip
> objcopy: debian/libqt5webenginecore5/usr/lib/i386-linux-gnu/libQt5WebEngineCore.so.5.7.1: unable to initialize compress status for section .debug_info
> objcopy:debian/libqt5webenginecore5/usr/lib/i386-linux-gnu/libQt5WebEngineCore.so.5.7.1: Memory exhausted
> dh_strip: objcopy --only-keep-debug --compress-debug-sections debian/libqt5webenginecore5/usr/lib/i386-linux-gnu/libQt5WebEngineCore.so.5.7.1 debian/.debhelper/libqt5webenginecore5/dbgsym-root/usr/lib/debug/.build-id/d4/c82995202e374ab64d53e8f6f30fd1f5f1866f.debug returned exit code 1
> debian/rules:68: recipe for target 'binary' failed
> make: *** [binary] Error 2
The full build log is available from:
http://aws-logs.debian.net/2017/06/01/qtwebengine-opensource-src_5.7.1+dfsg-6_testing-i386.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
Reply to: