[Pkg-javascript-devel] Bug#1009555: node-ini: FTBFS: ERROR: Coverage for statements (88.98%) does not meet global threshold (100%)

Lucas Nussbaum lucas at debian.org
Tue Apr 12 20:19:34 BST 2022


Source: node-ini
Version: 2.0.1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lucas at 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 ../. node_modules/ini
> 	/bin/sh -ex debian/tests/pkg-js/test
> + + grepls test/bar.js test/foo.js test/proto.js test/win32.js
>  -v test/foo.js
> + tap test/bar.js test/proto.js test/win32.js
> TAP version 13
> ok 1 - test/bar.js # time=31.642ms {
>     # Subtest: parse(stringify(x)) is same as x
>         # count=10
>         #  { count: 10 }
>         ok 1 - should be equivalent
>         # drink=white russian
>         #  { drink: 'white russian' }
>         ok 2 - should be equivalent
>         # isTrue=true
>         #  { isTrue: true }
>         ok 3 - should be equivalent
>         # [theDude]
>         # abides=true
>         # rugCount=1
>         #  { theDude: { abides: true, rugCount: 1 } }
>         ok 4 - should be equivalent
>         1..4
>     ok 1 - parse(stringify(x)) is same as x # time=24.752ms
>     
>     1..1
>     # time=31.642ms
> }
> 
> ok 2 - test/proto.js # time=6.257ms {
>     ok 1 - should be equivalent
>     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
>     1..12
>     # time=6.257ms
> }
> 
> ok 3 - test/win32.js # time=15.89ms {
>     ok 1 - should be equal
>     ok 2 - should be equal
>     ok 3 - should be equivalent
>     ok 4 - should be equivalent
>     ok 5 - should be equal
>     ok 6 - should be equal
>     ok 7 - should be equal
>     ok 8 - should be equal
>     1..8
>     # time=15.89ms
> }
> 
> 1..3
> # time=1346.938ms
> ERROR: Coverage for lines (88.79%) does not meet global threshold (100%)
> ERROR: Coverage for branches (83%) does not meet global threshold (100%)
> ERROR: Coverage for statements (88.98%) does not meet global threshold (100%)
> ----------|---------|----------|---------|---------|----------------------------------
> File      | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s                
> ----------|---------|----------|---------|---------|----------------------------------
> All files |   88.98 |       83 |     100 |   88.79 |                                  
>  ini.js   |   88.98 |       83 |     100 |   88.79 | 26-27,46,101,166-170,179-184,197 
> ----------|---------|----------|---------|---------|----------------------------------
> 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-ini_2.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=lucas@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220412&fusertaguser=lucas@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.



More information about the Pkg-javascript-devel mailing list