Source: node-output-file-sync Version: 2.0.1-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220412 ftbfs-bookworm
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary > 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/array-to-sentence > node_modules/array-to-sentence > ln -s ../debian/tests/test_modules/assert-valid-glob-opts > node_modules/assert-valid-glob-opts > ln -s ../debian/tests/test_modules/get-mode node_modules/get-mode > ln -s ../debian/tests/test_modules/glob-option-error > node_modules/glob-option-error > ln -s ../debian/tests/test_modules/indexed-filter > node_modules/indexed-filter > ln -s ../debian/tests/test_modules/inspect-with-kind > node_modules/inspect-with-kind > ln -s ../debian/tests/test_modules/is-utf8 node_modules/is-utf8 > ln -s ../debian/tests/test_modules/read-utf8-file > node_modules/read-utf8-file > ln -s ../debian/tests/test_modules/rmfr node_modules/rmfr > ln -s ../debian/tests/test_modules/validate-glob-opts > node_modules/validate-glob-opts > ln -s ../. node_modules/output-file-sync > /bin/sh -ex debian/tests/pkg-js/test > + tape test.js > TAP version 13 > # outputFileSync() > ok 1 should return null when it doesn't create any directories. > ok 2 should return the path of the first created directory. > ok 3 should throw an error when fs.writeFile fails. > ok 4 should throw an error when mkdirp fails. > ok 5 should reflect `mode` option to the directory mode. > ok 6 should reflect `mode` option to the file mode. > ok 7 should reflect `dirMode` option to the directory mode. > ok 8 should reflect `fileMode` option to the file mode. > ok 9 should create a file into the existing directory. > ok 10 should create a file into the new directory. > ok 11 should accept fs.writeFile's option. > # Argument validation for outputFileSync() > ok 12 should throw an error when it takes no arguments. > ok 13 should throw an error when the first argument is not a string. > ok 14 should throw an error when the first argument is an empty string. > not ok 15 should throw an error when the second argument is not a valid file > content. > --- > operator: throws > expected: |- > '/^TypeError.*Expected file content to be a string, Buffer or > Uint8Array, but got Set {} instead\\./' > actual: |- > { [TypeError: Expected file content to be a string, Buffer or > Uint8Array, but got Set(0) {} instead.] message: 'Expected file content to be > a string, Buffer or Uint8Array, but got Set(0) {} instead.' } > at: Test.<anonymous> (/<<PKGBUILDDIR>>/test.js:114:4) > stack: |- > TypeError: Expected file content to be a string, Buffer or Uint8Array, > but got Set(0) {} instead. > at outputFileSync (/<<PKGBUILDDIR>>/index.js:31:9) > at /<<PKGBUILDDIR>>/test.js:115:9 > at Test.throws (/usr/share/nodejs/tape/lib/test.js:632:9) > at Test.bound [as throws] (/usr/share/nodejs/tape/lib/test.js:99:32) > at Test.<anonymous> (/<<PKGBUILDDIR>>/test.js:114:4) > at Test.bound [as _cb] (/usr/share/nodejs/tape/lib/test.js:99:32) > at Test.run (/usr/share/nodejs/tape/lib/test.js:117:31) > at Test.bound [as run] (/usr/share/nodejs/tape/lib/test.js:99:32) > at Immediate.next [as _onImmediate] > (/usr/share/nodejs/tape/lib/results.js:88:19) > at processImmediate (internal/timers.js:464:21) > ... > ok 16 should throw an error when the third argument is provided but is > neither string nor an object. > not ok 17 should throw an error when the third argument is an invalid > encoding. > --- > operator: throws > expected: |- > '/^Error.*for exmaple \'utf8\' and \'ascii\', but got \'utf\\\\u0000\' > instead\\./' > actual: |- > { [Error: Expected a string to be a valid encoding, for exmaple 'utf8' > and 'ascii', but got 'utf\x00' instead.] message: 'Expected a string to be a > valid encoding, for exmaple \'utf8\' and \'ascii\', but got \'utf\\x00\' > instead.' } > at: Test.<anonymous> (/<<PKGBUILDDIR>>/test.js:126:4) > stack: |- > Error: Expected a string to be a valid encoding, for exmaple 'utf8' and > 'ascii', but got 'utf\x00' instead. > at outputFileSync (/<<PKGBUILDDIR>>/index.js:43:11) > at /<<PKGBUILDDIR>>/test.js:127:9 > at Test.throws (/usr/share/nodejs/tape/lib/test.js:632:9) > at Test.bound [as throws] (/usr/share/nodejs/tape/lib/test.js:99:32) > at Test.<anonymous> (/<<PKGBUILDDIR>>/test.js:126:4) > at Test.bound [as _cb] (/usr/share/nodejs/tape/lib/test.js:99:32) > at Test.run (/usr/share/nodejs/tape/lib/test.js:117:31) > at Test.bound [as run] (/usr/share/nodejs/tape/lib/test.js:99:32) > at Immediate.next [as _onImmediate] > (/usr/share/nodejs/tape/lib/results.js:88:19) > at processImmediate (internal/timers.js:464:21) > ... > ok 18 should throw an error when the third argument is an empty string. > ok 19 should throw an error when `encoding` option is not a string. > ok 20 should throw an error when `encoding` option is an empty string. > ok 21 should throw an error when `encoding` option is an invalid encoding. > ok 22 should throw an error when mode option is infinite. > ok 23 should throw an error when mode option exceeds the max safe integer. > ok 24 should throw an error when mode option is a negative number. > ok 25 should throw an error when mode option is a non-integer number. > ok 26 should throw an error when mode option is a non-integer number. > ok 27 should throw an error when mode option is an invalid octal. > ok 28 should throw an error when mode option is an invalid octal. > ok 29 should throw an error when mode option is neither string nor number. > > 1..29 > # tests 29 > # pass 27 > # fail 2 > > 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/2022/04/12/node-output-file-sync_2.0.1-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220412;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220412&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results 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.