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

[Lucas Nussbaum]

Source: node-browser-resolve
Version: 1.11.3-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 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-browser-resolve
> dpkg-buildpackage: info: source version 1.11.3-2
> 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-browser-resolve using existing ./node-browser-resolve_1.11.3.orig.tar.gz
> dpkg-source: info: building node-browser-resolve in node-browser-resolve_1.11.3-2.debian.tar.xz
> dpkg-source: info: building node-browser-resolve in node-browser-resolve_1.11.3-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
> 	mkdir -p node_modules
> 	ln -s ../. node_modules/browser-resolve
> 	/bin/sh -ex debian/tests/pkg-js/test
> + set -e
> + AUTOPKG=no
> + test no = no
> + mocha -R spec
> 
> ReferenceError: test is not defined
>     at Object.<anonymous> (/<<PKGBUILDDIR>>/test/core-sync.js:9:1)
>     at Module._compile (internal/modules/cjs/loader.js:1015:30)
>     at Object.Module._extensions..js (internal/modules/cjs/loader.js:1035:10)
>     at Module.load (internal/modules/cjs/loader.js:879:32)
>     at Function.Module._load (internal/modules/cjs/loader.js:724:14)
>     at Module.require (internal/modules/cjs/loader.js:903:19)
>     at require (internal/modules/cjs/helpers.js:74:18)
>     at Object.exports.requireOrImport (/usr/share/nodejs/mocha/lib/esm-utils.js:20:12)
>     at Object.exports.loadFilesAsync (/usr/share/nodejs/mocha/lib/esm-utils.js:33:34)
>     at Mocha.loadFilesAsync (/usr/share/nodejs/mocha/lib/mocha.js:431:19)
>     at singleRun (/usr/share/nodejs/mocha/lib/cli/run-helpers.js:125:15)
>     at exports.runMocha (/usr/share/nodejs/mocha/lib/cli/run-helpers.js:190:10)
>     at Object.exports.handler (/usr/share/nodejs/mocha/lib/cli/run.js:362:11)
>     at /usr/share/nodejs/yargs/lib/command.js:238:63
> 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/12/26/node-browser-resolve_1.11.3-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!

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 me
so that we can identify if something relevant changed in the meantime.

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.