[Pkg-javascript-devel] Bug#1009571: node-call-limit: FTBFS: ERROR: Coverage for statements (83.58%) does not meet global threshold (100%)

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


Source: node-call-limit
Version: 1.1.1-2
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/call-limit
> 	/bin/sh -ex debian/tests/pkg-js/test
> + tap -J -R spec test/limit.js
> 
> (node:1484220) DeprecationWarning: is() is deprecated, use equal() instead
> (Use `node --trace-deprecation ...` to show where the warning was created)
> test/limit.js
>   limit
> 
>     ✓ Immediately queued 2 callbacks
> 
>     ✓ With no completion yet
> 
>     ✓ Calling the finisher completed the first one
> 
>     ✓ Third action was started
> 
>     ✓ All completed
> 
>   limit-obj-method
> 
>     ✓ Immediately queued 2 callbacks
> 
>     ✓ With no completion yet
> 
>     ✓ Calling the finisher completed the first one
> 
>     ✓ Third action was started
> 
>     ✓ All completed
> 
>   limit-class-method
> 
>     ✓ Immediately queued 2 callbacks
> 
>     ✓ With no completion yet
> 
>     ✓ Calling the finisher completed the first one
> 
>     ✓ Third action was started
> 
>     ✓ All completed
> 
>   promise
> 
>     ✓ Immediately queued 2 callbacks
> 
>     ✓ With no completion yet
> 
>     ✓ Calling the finisher completed the first one
> 
>     ✓ Third action was started
> 
>     ✓ All completed
> 
>   limit-promiseobj-method
> 
>     ✓ Immediately queued 2 callbacks
> 
>     ✓ With no completion yet
> 
>     ✓ Calling the finisher completed the first one
> 
>     ✓ Third action was started
> 
>     ✓ All completed
> 
>   limit-promiseclass-method
> 
>     ✓ Immediately queued 2 callbacks
> 
>     ✓ With no completion yet
> 
>     ✓ Calling the finisher completed the first one
> 
>     ✓ Third action was started
> 
>     ✓ All completed
> 
> 
>   30 passing (738.136ms)
> ERROR: Coverage for lines (88.13%) does not meet global threshold (100%)
> ERROR: Coverage for functions (89.47%) does not meet global threshold (100%)
> ERROR: Coverage for branches (77.27%) does not meet global threshold (100%)
> ERROR: Coverage for statements (83.58%) does not meet global threshold (100%)
> ---------------|---------|----------|---------|---------|-------------------
> File           | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s 
> ---------------|---------|----------|---------|---------|-------------------
> All files      |   83.58 |    77.27 |   89.47 |   88.13 |                   
>  call-limit.js |   83.58 |    77.27 |   89.47 |   88.13 | 31-33,81-86       
> ---------------|---------|----------|---------|---------|-------------------
> 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-call-limit_1.1.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=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