Source: node-rimraf
Version: 3.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/rimraf -> ../../types-rimraf
> 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/rimraf
> /bin/sh -ex debian/tests/pkg-js/test
> + tap test/basic.js test/bin.js test/custom-fs.js test/fill.js
> TAP version 13
> (node:571502) DeprecationWarning: notEqual() is deprecated, use not() instead
> (Use `node --trace-deprecation ...` to show where the warning was created)
> ok 1 - test/basic.js # time=278.462ms {
> # Subtest: initial clean
> ok 1 - expected to throw
> 1..1
> ok 1 - initial clean # time=8.001ms
>
> # Subtest: sync removal
> ok 1 - expect truthy value
> ok 2 - expected to throw
> 1..2
> ok 2 - sync removal # time=44.787ms
>
> # Subtest: async removal
> ok 1 - expect truthy value
> ok 2 - expected to throw
> 1..2
> ok 3 - async removal # time=46.058ms
>
> # Subtest: glob
> 1..2
> # Subtest: async
> ok 1 - should not be equal
> ok 2 - should be equivalent
> 1..2
> ok 1 - async # time=53.775ms
>
> # Subtest: sync
> ok 1 - should not be equal
> ok 2 - should be equivalent
> 1..2
> ok 2 - sync # time=22.388ms
>
> ok 4 - glob # time=83.602ms
>
> # Subtest: no glob
> 1..2
> # Subtest: async
> ok 1 - should not be equal
> ok 2 - should be equivalent
> 1..2
> ok 1 - async # time=29.76ms
>
> # Subtest: sync
> ok 1 - should not be equal
> ok 2 - should be equivalent
> 1..2
> ok 2 - sync # time=28.6ms
>
> ok 5 - no glob # time=63.384ms
>
> # Subtest: verify that cleanup happened
> ok 1 - expected to throw
> ok 2 - expected to throw
> 1..2
> ok 6 - verify that cleanup happened # time=1.482ms
>
> 1..6
> # time=278.462ms
> }
>
> ok 2 - test/bin.js # time=2208.325ms {
> # Subtest: setup
> 1..0
> ok 1 - setup # time=8.14ms
>
> # Subtest: help
> 1..4
> # Subtest: -help
> ok 1 - should be equal
> ok 2 - should be equal
> ok 3 - should match pattern provided
> 1..3
> ok 1 - -help # time=591.596ms
>
> # Subtest: -h
> ok 1 - should be equal
> ok 2 - should be equal
> ok 3 - should match pattern provided
> 1..3
> ok 2 - -h # time=225.477ms
>
> # Subtest: --help
> ok 1 - should be equal
> ok 2 - should be equal
> ok 3 - should match pattern provided
> 1..3
> ok 3 - --help # time=226.234ms
>
> # Subtest: --?
> ok 1 - should be equal
> ok 2 - should be equal
> ok 3 - should match pattern provided
> 1..3
> ok 4 - --? # time=220.572ms
>
> ok 2 - help # time=1269.211ms
>
> # Subtest: glob, but matches
> ok 1 - should be equal
> ok 2 - expected to throw
> ok 3 - bound statSync
> 1..3
> ok 3 - glob, but matches # time=227.621ms
>
> # Subtest: --no-glob
> 1..2
> # Subtest: no glob with *.txt
> ok 1 - should be equal
> ok 2 - expected to throw
> ok 3 - bound statSync
> 1..3
> ok 1 - no glob with *.txt # time=230.222ms
>
> # Subtest: no glob with dir star
> ok 1 - should be equal
> ok 2 - expected to throw
> ok 3 - bound statSync
> 1..3
> ok 2 - no glob with dir star # time=225.962ms
>
> ok 4 - --no-glob # time=460.664ms
>
> # Subtest: glob, but no exact match
> ok 1 - should be equal
> ok 2 - expected to throw
> ok 3 - expected to throw
> ok 4 - expected to throw
> ok 5 - expected to throw
> 1..5
> ok 5 - glob, but no exact match # time=228.399ms
>
> # Subtest: cleanup
> 1..0
> ok 6 - cleanup # time=5.467ms
>
> 1..6
> # time=2208.325ms
> }
>
> ok 3 - test/custom-fs.js # time=45.555ms {
> # Subtest: setup
> 1..0
> ok 1 - setup # time=4.697ms
>
> # Subtest: rimraf with interceptor
> ok 1 - should be equivalent strictly
> 1..1
> ok 2 - rimraf with interceptor # time=17.126ms
>
> # Subtest: rimraf sync with interceptor
> ok 1 - should be equivalent strictly
> 1..1
> ok 3 - rimraf sync with interceptor # time=9.365ms
>
> # Subtest: cleanup
> ok 1 - expected to throw
> 1..1
> ok 4 - cleanup # time=3.841ms
>
> 1..4
> # time=45.555ms
> }
>
> ok 4 - test/fill.js # time=5.805ms {
> ok 1 - yes
> 1..1
> # time=5.805ms
> }
>
> 1..4
> # time=3319.634ms
> ERROR: Coverage for lines (73.04%) does not meet global threshold (100%)
> ERROR: Coverage for functions (81.81%) does not meet global threshold (100%)
> ERROR: Coverage for branches (55.37%) does not meet global threshold (100%)
> ERROR: Coverage for statements (72.51%) does not meet global threshold (100%)
> -----------|---------|----------|---------|---------|-----------------------------------------------
> File | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s
>
> -----------|---------|----------|---------|---------|-----------------------------------------------
> All files | 72.51 | 55.37 | 81.81 | 73.04 |
>
> bin.js | 85.45 | 76.31 | 100 | 85.18 | 11-12,23,25,29,33,35,46
>
> rimraf.js | 69.08 | 50 | 77.77 | 69.8 |
> ...40,245,247,281,294-295,305-312,325,327,354
> -----------|---------|----------|---------|---------|-----------------------------------------------
> 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-rimraf_3.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.
