[Pkg-javascript-devel] Bug#1009539: node-har-validator: FTBFS: ERROR: Coverage for statements (83.33%) does not meet global threshold (100%)

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


Source: node-har-validator
Version: 5.1.5-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/har-validator
> 	/bin/sh -ex debian/tests/pkg-js/test
> + tap test --reporter spec
> 
> test/async.js
>   async
> 
>     ✓ afterRequest is a function
> 
>     ✓ beforeRequest is a function
> 
>     ✓ browser is a function
> 
>     ✓ cache is a function
> 
>     ✓ content is a function
> 
>     ✓ cookie is a function
> 
>     ✓ creator is a function
> 
>     ✓ entry is a function
> 
>     ✓ har is a function
> 
>     ✓ header is a function
> 
>     ✓ log is a function
> 
>     ✓ page is a function
> 
>     ✓ pageTimings is a function
> 
>     ✓ postData is a function
> 
>     ✓ query is a function
> 
>     ✓ request is a function
> 
>     ✓ response is a function
> 
>     ✓ timings is a function
> 
>   failure
> 
>     ✓ should fail
> 
>     ✓ should return false in a callback
> 
>     ✓ should return HARError object in a callback
> 
>     ✓ should fail on bad "log.version"
> 
>   success
> 
>     ✓ should be successful
> 
>     ✓ should return true in a callback
> 
>     ✓ should not have any errors
> 
> test/cache-entry.js
>   cache entry
> 
>     ✓ should allow null beforeRequest
> 
>     ✓ should allow null afterRequest
> 
> test/log.js
>   log
> 
>     ✓ should fail with empty object
> 
>     ✓ should fail with empty array
> 
>     ✓ should fail with undefined
> 
>     ✓ should fail on bad "log.version"
> 
>     ✓ should fail on bad "log.creator"
> 
>     ✓ should fail on bad "log.pages.*.startedDateTime"
> 
>     ✓ should not fail with full example
> 
> test/promise.js
>   promises
> 
>     ✓ afterRequest is a function
> 
>     ✓ afterRequest() is a promise
> 
>     ✓ beforeRequest is a function
> 
>     ✓ beforeRequest() is a promise
> 
>     ✓ browser is a function
> 
>     ✓ browser() is a promise
> 
>     ✓ cache is a function
> 
>     ✓ cache() is a promise
> 
>     ✓ content is a function
> 
>     ✓ content() is a promise
> 
>     ✓ cookie is a function
> 
>     ✓ cookie() is a promise
> 
>     ✓ creator is a function
> 
>     ✓ creator() is a promise
> 
>     ✓ entry is a function
> 
>     ✓ entry() is a promise
> 
>     ✓ har is a function
> 
>     ✓ har() is a promise
> 
>     ✓ header is a function
> 
>     ✓ header() is a promise
> 
>     ✓ log is a function
> 
>     ✓ log() is a promise
> 
>     ✓ page is a function
> 
>     ✓ page() is a promise
> 
>     ✓ pageTimings is a function
> 
>     ✓ pageTimings() is a promise
> 
>     ✓ postData is a function
> 
>     ✓ postData() is a promise
> 
>     ✓ query is a function
> 
>     ✓ query() is a promise
> 
>     ✓ request is a function
> 
>     ✓ request() is a promise
> 
>     ✓ response is a function
> 
>     ✓ response() is a promise
> 
>     ✓ timings is a function
> 
>     ✓ timings() is a promise
> 
>     ✓ thrown error is an object
> 
>     ✓ resolves with the original data
> 
> test/request.js
>   request
> 
>     ✓ should fail with empty object
> 
>     ✓ should fail with empty array
> 
>     ✓ should fail with undefined
> 
>     ✓ should fail on bad "url"
> 
>     ✓ should fail on bad "headers"
> 
>     ✓ should fail on malformed "headers"
> 
>     ✓ should not fail with full example
> 
> test/response.js
>   response
> 
>     ✓ should fail with empty object
> 
>     ✓ should fail with empty array
> 
>     ✓ should fail with undefined
> 
>     ✓ should fail on bad "bodySize"
> 
>     ✓ should fail on bad "headers"
> 
>     ✓ should fail on malformed "headers"
> 
>     ✓ should not fail with full example
> 
> 
>   86 passing (1s)
> ERROR: Coverage for lines (83.33%) does not meet global threshold (100%)
> ERROR: Coverage for functions (59.52%) does not meet global threshold (100%)
> ERROR: Coverage for branches (87.5%) does not meet global threshold (100%)
> ERROR: Coverage for statements (83.33%) does not meet global threshold (100%)
> ------------|---------|----------|---------|---------|----------------------------------------------
> File        | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s                            
> ------------|---------|----------|---------|---------|----------------------------------------------
> All files   |   83.33 |     87.5 |   59.52 |   83.33 |                                              
>  async.js   |      66 |     87.5 |      15 |      66 | ...,52,56,60,64,72,76,80,84,88,92,96,100,104 
>  error.js   |   88.88 |       50 |     100 |   88.88 | 11                                           
>  promise.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-har-validator_5.1.5-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