Source: node-pump
Version: 3.0.0-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> dpkg-buildpackage
> -----------------
>
> Command: dpkg-buildpackage -us -uc -sa -rfakeroot
> dpkg-buildpackage: info: source package node-pump
> dpkg-buildpackage: info: source version 3.0.0-2
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Xavier Guimard <y...@debian.org>
> dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
> debian/rules clean
> dh clean --with nodejs
> dh_auto_clean --buildsystem=nodejs
> rm -rf ./node_modules/.cache
> dh_clean
> dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building node-pump using existing
> ./node-pump_3.0.0.orig.tar.gz
> dpkg-source: info: building node-pump in node-pump_3.0.0-2.debian.tar.xz
> dpkg-source: info: building node-pump in node-pump_3.0.0-2.dsc
> debian/rules binary
> dh binary --with nodejs
> dh_update_autotools_config
> dh_autoreconf
> dh_auto_configure --buildsystem=nodejs
> dh_auto_build --buildsystem=nodejs
> No build command found, searching known files
> dh_auto_test --buildsystem=nodejs
> /bin/sh -ex debian/tests/pkg-js/test
> + set -e
> + set -x
> + node ./test-node.js
> /<<PKGBUILDDIR>>/test-node.js:52
> throw new Error('timeout')
> ^
>
> Error: timeout
> at Timeout._onTimeout (/<<PKGBUILDDIR>>/test-node.js:52:9)
> at listOnTimeout (internal/timers.js:549:17)
> at processTimers (internal/timers.js:492:7)
> dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1
The full build log is available from:
http://qa-logs.debian.net/2020/06/20/node-pump_3.0.0-2_unstable.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.
