Source: node-mkdirp
Version: 1.0.4+~1.0.2-1
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
> Link node_modules/@types/mkdirp -> ../../types-mkdirp
> dh_auto_build --buildsystem=nodejs
> No build command found, searching known files
> No build command found, searching known files
> dh_auto_test --buildsystem=nodejs
> ln -s ../. node_modules/mkdirp
> /bin/sh -ex debian/tests/pkg-js/test
> + ls test/cmd.js test/find-made.js test/index.js test/mkdirp-manual.js+
> test/mkdirp-native.js test/opts-arg.jsgrep -v test/cmd
> + grep -v test/find-made
> test/path-arg.js test/use-native.js
> + grep -v test/index
> + tap test/mkdirp-manual.js test/mkdirp-native.js test/opts-arg.js
> test/path-arg.js test/use-native.js
> TAP version 13
> ok 1 - test/mkdirp-manual.js # time=45.264ms {
> # Subtest: mkdirpManual / just calls implementation
> # Subtest: success is fine, of course
> ok 1 - should be equal
> ok 2 - should be equal
> ok 3 - should be equal
> ok 4 - should be equal
> 1..4
> ok 1 - success is fine, of course # time=11.718ms
>
> # Subtest: EISDIR is expected and ignored
> ok 1 - should be equal
> ok 2 - should be equal
> ok 3 - should be equal
> ok 4 - should be equal
> 1..4
> ok 2 - EISDIR is expected and ignored # time=2.049ms
>
> # Subtest: other failures are failures
> ok 1 - expected to throw
> ok 2 - expect rejected Promise
> 1..2
> ok 3 - other failures are failures # time=6.534ms
>
> 1..3
> ok 1 - mkdirpManual / just calls implementation # time=33.378ms
>
> # Subtest: unknown failure types are failures
> ok 1 - expected to throw
> ok 2 - expect rejected Promise
> 1..2
> ok 2 - unknown failure types are failures # time=1.812ms
>
> 1..2
> # time=45.264ms
> }
>
> ok 2 - test/mkdirp-native.js # time=25.452ms {
> # Subtest: mkdirpNative / just calls implementation
> ok 1 - should be equal
> ok 2 - should be equal
> ok 3 - should be equal
> ok 4 - should be equal
> 1..4
> ok 1 - mkdirpNative / just calls implementation # time=7.155ms
>
> # Subtest: other errors are raised to caller
> ok 1 - expected to throw
> ok 2 - expect rejected Promise
> 1..2
> ok 2 - other errors are raised to caller # time=10.198ms
>
> 1..2
> # time=25.452ms
> }
>
> ok 3 - test/opts-arg.js # time=37.199ms {
> ok 1 - null
> ok 2 - false
> ok 3 - undefined
> ok 4 - empty object
> ok 5 - numeric mode
> ok 6 - string mode
> ok 7 - empty custom fs
> ok 8 - custom stat/statSync
> ok 9 - custom fs with stat/statSync
> ok 10 - expected to throw: TypeError invalid options argument
> 1..10
> # time=37.199ms
> }
>
> ok 4 - test/path-arg.js # time=799.022ms {
> # Subtest: node ./test/path-arg.js
> ok 1 - should be equal
> ok 2 - expected to throw: Error path must be a string without null
> bytes
> ok 3 - expected to throw: Error Illegal characters in path
> ok 4 - expected to throw: Error Illegal characters in path
> ok 5 - expected to throw: Error Illegal characters in path
> ok 6 - expected to throw: Error Illegal characters in path
> ok 7 - expected to throw: Error Illegal characters in path
> ok 8 - expected to throw: Error Illegal characters in path
> ok 9 - expected to throw: Error Illegal characters in path
> 1..9
> # time=21.664ms
> ok 1 - node ./test/path-arg.js # time=21.664ms
>
> ok 2 - should be equal
> ok 3 - expected to throw: Error path must be a string without null bytes
> 1..3
> # time=799.022ms
> }
>
> ok 5 - test/use-native.js # time=630.964ms {
> # Subtest: node ./test/use-native.js
> ok 1 - should be equal
> ok 2 - should be equal
> ok 3 - should be equal
> ok 4 - should be equal
> 1..4
> # time=8.048ms
> ok 1 - node ./test/use-native.js # time=8.048ms
>
> # Subtest: node ./test/use-native.js
> ok 1 - should be equal
> ok 2 - should be equal
> ok 3 - should be equal
> ok 4 - should be equal
> 1..4
> # time=5.229ms
> ok 2 - node ./test/use-native.js # time=5.229ms
>
> ok 3 - should be equal
> ok 4 - should be equal
> ok 5 - should be equal
> ok 6 - should be equal
> 1..6
> # time=630.964ms
> }
>
> 1..5
> # time=1593.861ms
> ERROR: Coverage for lines (84.9%) does not meet global threshold (100%)
> ERROR: Coverage for functions (73.68%) does not meet global threshold (100%)
> ERROR: Coverage for branches (80.82%) does not meet global threshold (100%)
> ERROR: Coverage for statements (83.92%) does not meet global threshold (100%)
> ------------------|---------|----------|---------|---------|-------------------------
> File | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line
> #s
> ------------------|---------|----------|---------|---------|-------------------------
> All files | 83.92 | 80.82 | 73.68 | 84.9 |
>
> mkdirp-manual.js | 65.85 | 57.14 | 50 | 67.5 |
> 17-18,21-26,49,52,55-59
> mkdirp-native.js | 85.18 | 75 | 80 | 88.46 | 15,30,33
>
> opts-arg.js | 100 | 100 | 100 | 100 |
>
> path-arg.js | 100 | 100 | 100 | 100 |
>
> use-native.js | 100 | 100 | 100 | 100 |
>
> ------------------|---------|----------|---------|---------|-------------------------
> 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-mkdirp_1.0.4+~1.0.2-1_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.
