[Pkg-javascript-devel] Bug#954508: node-gulp-flatten: FTBFS: dh_auto_test: error: /bin/sh -e debian/tests/pkg-js/test returned exit code 1

[Lucas Nussbaum]

Source: node-gulp-flatten
Version: 0.4.0-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200321 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-gulp-flatten
> dpkg-buildpackage: info: source version 0.4.0-3
> 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-gulp-flatten using existing ./node-gulp-flatten_0.4.0.orig.tar.gz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: info: building node-gulp-flatten in node-gulp-flatten_0.4.0-3.debian.tar.xz
> dpkg-source: info: building node-gulp-flatten in node-gulp-flatten_0.4.0-3.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 -e debian/tests/pkg-js/test
> 
> 
>   gulp-flatten
>     includeParents
>       ✓ should keep top parent dirs from indludeParents option
>       ✓ should keep bottom parent dirs from indludeParents option
>       ✓ should treat negative number in indludeParents as bottom parent levels
>       ✓ should keep top and bottom parent dirs from indludeParents option
>       ✓ should pick relative path if indludeParents bottom+top too long
>     subPath
>       ✓ should keep top parent dirs from subPath option
>       ✓ should keep bottom parent dirs from subPath option
>       ✓ should keep top2 and bottom2 from subPath option
> 
>   gulp-flatten
>     flatten()
>       ✓ should strip relative path without options
>       ✓ should replace relative path with option path
>       - should emit arg error with nonstring option
>       1) should ignore directories
>       ✓ should strip relative path at the specified depth if depth option is passed
>       ✓ should leave path from the end if depth option is passed as negative number
>       ✓ should make no changes if the absolute depth option is greater than the tree depth
> 
> 
>   13 passing (19ms)
>   1 pending
>   1 failing
> 
>   1) gulp-flatten
>        flatten()
>          should ignore directories:
>      TypeError: gulp.start is not a function
>       at Context.<anonymous> (test/main.js:77:12)
>       at callFnAsync (/usr/share/nodejs/mocha/lib/runnable.js:423:21)
>       at Test.Runnable.run (/usr/share/nodejs/mocha/lib/runnable.js:363:7)
>       at Runner.runTest (/usr/share/nodejs/mocha/lib/runner.js:541:10)
>       at /usr/share/nodejs/mocha/lib/runner.js:667:12
>       at next (/usr/share/nodejs/mocha/lib/runner.js:450:14)
>       at /usr/share/nodejs/mocha/lib/runner.js:460:7
>       at next (/usr/share/nodejs/mocha/lib/runner.js:362:14)
>       at Immediate._onImmediate (/usr/share/nodejs/mocha/lib/runner.js:428:5)
>       at process.topLevelDomainCallback (domain.js:126:23)
> 
> 
> 
> dh_auto_test: error: /bin/sh -e debian/tests/pkg-js/test returned exit code 1

The full build log is available from:
   http://qa-logs.debian.net/2020/03/21/node-gulp-flatten_0.4.0-3_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.