[Pkg-javascript-devel] Bug#997583: node-stream-each: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1

[Lucas Nussbaum]

Source: node-stream-each
Version: 1.2.3-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lucas at debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm

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-stream-each
> dpkg-buildpackage: info: source version 1.2.3-1
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Xavier Guimard <yadd at 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-stream-each using existing ./node-stream-each_1.2.3.orig.tar.gz
> dpkg-source: info: building node-stream-each in node-stream-each_1.2.3-1.debian.tar.xz
> dpkg-source: info: building node-stream-each in node-stream-each_1.2.3-1.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
> 	mkdir -p node_modules
> 	ln -s ../debian/tests/test_modules/ndjson node_modules/ndjson
> 	ln -s ../. node_modules/stream-each
> 	/bin/sh -ex debian/tests/pkg-js/test
> + NODE_PATH=debian/tests/test_modules tape test.js
> TAP version 13
> # each
> ok 1 should be deeply equivalent
> ok 2 should be deeply equivalent
> ok 3 should be deeply equivalent
> # each and callback
> ok 4 should be deeply equivalent
> ok 5 should be deeply equivalent
> ok 6 should be deeply equivalent
> # each (write after)
> ok 7 should be deeply equivalent
> ok 8 should be deeply equivalent
> ok 9 should be deeply equivalent
> # each error
> ok 10 should be deeply equivalent
> # each error and callback
> ok 11 should be deeply equivalent
> # each with falsey values
> ok 12 should be deeply equivalent
> ok 13 should be deeply equivalent
> not ok 14 .end() already called: should be deeply equivalent
>   ---
>     operator: fail
>     at: <anonymous> (/<<PKGBUILDDIR>>/test.js:103:7)
>     stack: |-
>       Error: .end() already called: should be deeply equivalent
>           at Test.assert [as _assert] (/usr/share/nodejs/tape/lib/test.js:311:54)
>           at Test.bound [as _assert] (/usr/share/nodejs/tape/lib/test.js:96:32)
>           at Test.fail (/usr/share/nodejs/tape/lib/test.js:405:10)
>           at Test.bound [as fail] (/usr/share/nodejs/tape/lib/test.js:96:32)
>           at Test.assert [as _assert] (/usr/share/nodejs/tape/lib/test.js:289:14)
>           at Test.bound [as _assert] (/usr/share/nodejs/tape/lib/test.js:96:32)
>           at Test.tapeDeepEqual (/usr/share/nodejs/tape/lib/test.js:552:10)
>           at Test.bound [as same] (/usr/share/nodejs/tape/lib/test.js:96:32)
>           at /<<PKGBUILDDIR>>/test.js:103:7
>           at Transform.done (/<<PKGBUILDDIR>>/index.js:22:19)
>   ...
> # huge stack
> ok 15 no error
> # cb only once
> ok 16 only once
> ok 17 had error
> 
> 1..17
> # tests 17
> # pass  16
> # fail  1
> 
> 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/2021/10/23/node-stream-each_1.2.3-1_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!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.