Source: node-mute-stream
Version: 0.0.8+~0.0.1-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/mute-stream -> ../../types-mute-stream
> 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/mute-stream
> /bin/sh -ex debian/tests/pkg-js/test
> + tap test
> TAP version 13
> ok 1 - test/basic.js # time=25.16ms {
> # Subtest: incoming
> ok 1 - should be equal
> ok 2 - should be equal
> ok 3 - should be equal
> 1..3
> ok 1 - incoming # time=5.356ms
>
> # Subtest: outgoing
> ok 1 - should be equal
> ok 2 - should be equal
> ok 3 - should be equal
> 1..3
> ok 2 - outgoing # time=1.268ms
>
> # Subtest: isTTY
> ok 1 - should be equal
> ok 2 - should be equal
> ok 3 - should be equal
> ok 4 - should be equal
> ok 5 - should be equal
> ok 6 - should be equal
> ok 7 - should be equal
> ok 8 - should be equal
> ok 9 - should be equal
> ok 10 - should be equal
> ok 11 - should be equal
> ok 12 - should be equal
> ok 13 - should be equal
> ok 14 - should be equal
> ok 15 - should be equal
> ok 16 - should be equal
> ok 17 - should be equal
> ok 18 - should be equal
> ok 19 - should be equal
> ok 20 - should be equal
> 1..20
> ok 3 - isTTY # time=2.839ms
>
> # Subtest: pause/resume incoming
> ok 1 - should be equal
> ok 2 - should be equal
> ok 3 - should be equal
> ok 4 - should be equal
> ok 5 - saw all events
> 1..5
> ok 4 - pause/resume incoming # time=1.175ms
>
> # Subtest: replace with *
> ok 1 - should be equal
> ok 2 - should be equal
> ok 3 - should be equal
> ok 4 - should be equal
> ok 5 - should be equal
> ok 6 - should be equal
> ok 7 - should be equal
> ok 8 - should be equal
> ok 9 - should be equal
> 1..9
> ok 5 - replace with * # time=1.679ms
>
> # Subtest: replace with ~YARG~
> ok 1 - should be equal
> ok 2 - should be equal
> ok 3 - should be equal
> ok 4 - should be equal
> ok 5 - should be equal
> ok 6 - should be equal
> ok 7 - should be equal
> ok 8 - should be equal
> ok 9 - should be equal
> 1..9
> ok 6 - replace with ~YARG~ # time=1.206ms
>
> 1..6
> # time=25.16ms
> }
>
> 1..1
> # time=721.218ms
> ERROR: Coverage for lines (77.77%) does not meet global threshold (100%)
> ERROR: Coverage for functions (93.33%) does not meet global threshold (100%)
> ERROR: Coverage for branches (57.14%) does not meet global threshold (100%)
> ERROR: Coverage for statements (75.36%) does not meet global threshold (100%)
> ----------|---------|----------|---------|---------|-----------------------------
> File | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s
>
> ----------|---------|----------|---------|---------|-----------------------------
> All files | 75.36 | 57.14 | 93.33 | 77.77 |
>
> mute.js | 75.36 | 57.14 | 93.33 | 77.77 |
> 104-110,114-116,127,137-140
> ----------|---------|----------|---------|---------|-----------------------------
> 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-mute-stream_0.0.8+~0.0.1-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.
