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

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


Source: node-dashdash
Version: 2.0.0-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/dashdash
> 	/bin/sh -ex debian/tests/pkg-js/test
> + tap test/basics.test.js
> TAP version 13
> (node:3375378) DeprecationWarning: deepEqual() is deprecated, use same() instead
> (Use `node --trace-deprecation ...` to show where the warning was created)
> ok 1 - test/basics.test.js # time=322.339ms {
>     # Subtest: exports
>         ok 1 - dashdash.createParser
>         ok 2 - dashdash.parse
>         ok 3 - dashdash.Parser
>         1..3
>     ok 1 - exports # time=5.769ms
>     
>     # Subtest: createParser
>         ok 1 - expect truthy value
>         1..1
>     ok 2 - createParser # time=2.393ms
>     
>     # Subtest: Parser
>         ok 1 - expect truthy value
>         1..1
>     ok 3 - Parser # time=0.83ms
>     
>     # Subtest: parse
>         ok 1 - expect truthy value
>         1..1
>     ok 4 - parse # time=2.117ms
>     
>     # Subtest: old Parser.parse() API
>         ok 1 - expect truthy value
>         ok 2 - expect truthy value
>         1..2
>     ok 5 - old Parser.parse() API # time=1.271ms
>     
>     # Subtest: slice
>         ok 1 - expect truthy value
>         ok 2 - should be equal
>         ok 3 - expect truthy value
>         ok 4 - should be equal
>         1..4
>     ok 6 - slice # time=1.343ms
>     
>     # Subtest: synopsisFromOpt
>         ok 1 - should be equal
>         ok 2 - should be equal
>         1..2
>     ok 7 - synopsisFromOpt # time=1.26ms
>     
>     # Subtest: case 0: node tool.js
>         ok 1 - should be equivalent
>         1..1
>     ok 8 - case 0: node tool.js # time=5.738ms
>     
>     # Subtest: case 1: node tool.js a b c
>         ok 1 - should be equivalent
>         1..1
>     ok 9 - case 1: node tool.js a b c # time=1.898ms
>     
>     # Subtest: case 2: node tool.js a b
>         ok 1 - should be equivalent
>         1..1
>     ok 10 - case 2: node tool.js a b # time=1.186ms
>     
>     # Subtest: case 3: node tool.js -- a
>         ok 1 - should be equivalent
>         1..1
>     ok 11 - case 3: node tool.js -- a # time=0.889ms
>     
>     # Subtest: case 4: node tool.js a -- b
>         ok 1 - should be equivalent
>         1..1
>     ok 12 - case 4: node tool.js a -- b # time=0.946ms
>     
>     # Subtest: case 5: node tool.js a -- --help
>         ok 1 - should be equivalent
>         1..1
>     ok 13 - case 5: node tool.js a -- --help # time=0.731ms
>     
>     # Subtest: case 6: node tool.js --help
>         ok 1 - should be equivalent
>         1..1
>     ok 14 - case 6: node tool.js --help # time=0.778ms
>     
>     # Subtest: case 7: node tool.js --help a b
>         ok 1 - should be equivalent
>         1..1
>     ok 15 - case 7: node tool.js --help a b # time=1.035ms
>     
>     # Subtest: case 8: node tool.js a --help b
>         ok 1 - should be equivalent
>         1..1
>     ok 16 - case 8: node tool.js a --help b # time=1.008ms
>     
>     # Subtest: case 9: node tool.js a --help b
>         ok 1 - should be equivalent
>         1..1
>     ok 17 - case 9: node tool.js a --help b # time=1.004ms
>     
>     # Subtest: case 10: node tool.js a --help b
>         ok 1 - should be equivalent
>         1..1
>     ok 18 - case 10: node tool.js a --help b # time=0.904ms
>     
>     # Subtest: case 11: node tool.js --help=foo
>         ok 1 - error message did not match /argument given to .* option that does not take one/: "argument given to "--help" option that does not take one: "--help=foo""
>         ok 2 - expected an error
>         1..2
>     ok 19 - case 11: node tool.js --help=foo # time=2.227ms
>     
>     # Subtest: case 12: node tool.js --file
>         ok 1 - error message did not match /do not have enough args/: "do not have enough args for "--file" option"
>         ok 2 - expected an error
>         1..2
>     ok 20 - case 12: node tool.js --file # time=0.727ms
>     
>     # Subtest: case 13: node tool.js
>         ok 1 - should be equivalent
>         1..1
>     ok 21 - case 13: node tool.js # time=0.798ms
>     
>     # Subtest: case 14: node tool.js --file foo.txt
>         ok 1 - should be equivalent
>         1..1
>     ok 22 - case 14: node tool.js --file foo.txt # time=0.868ms
>     
>     # Subtest: case 15: node tool.js --file=foo.txt
>         ok 1 - should be equivalent
>         1..1
>     ok 23 - case 15: node tool.js --file=foo.txt # time=0.785ms
>     
>     # Subtest: case 16: node tool.js -
>         ok 1 - should be equivalent
>         1..1
>     ok 24 - case 16: node tool.js - # time=0.843ms
>     
>     # Subtest: case 17: node tool.js -h
>         ok 1 - should be equivalent
>         1..1
>     ok 25 - case 17: node tool.js -h # time=0.739ms
>     
>     # Subtest: case 18: node tool.js -f
>         ok 1 - error message did not match /do not have enough args/: "do not have enough args for "-f" option"
>         ok 2 - expected an error
>         1..2
>     ok 26 - case 18: node tool.js -f # time=0.619ms
>     
>     # Subtest: case 19: node tool.js -f foo.txt
>         ok 1 - should be equivalent
>         1..1
>     ok 27 - case 19: node tool.js -f foo.txt # time=0.651ms
>     
>     # Subtest: case 20: node tool.js -ffoo.txt
>         ok 1 - should be equivalent
>         1..1
>     ok 28 - case 20: node tool.js -ffoo.txt # time=0.691ms
>     
>     # Subtest: case 21: node ls.js -l -a dir
>         ok 1 - should be equivalent
>         1..1
>     ok 29 - case 21: node ls.js -l -a dir # time=1.25ms
>     
>     # Subtest: case 22: node ls.js -l dir -a
>         ok 1 - should be equivalent
>         1..1
>     ok 30 - case 22: node ls.js -l dir -a # time=1.149ms
>     
>     # Subtest: case 23: node ls.js -l dir -a
>         ok 1 - should be equivalent
>         1..1
>     ok 31 - case 23: node ls.js -l dir -a # time=1.036ms
>     
>     # Subtest: case 24: node ls.js -la dir
>         ok 1 - should be equivalent
>         1..1
>     ok 32 - case 24: node ls.js -la dir # time=0.881ms
>     
>     # Subtest: case 25: node tool.js -af
>         ok 1 - error message did not match /do not have enough args/: "do not have enough args for "-f" option"
>         ok 2 - expected an error
>         1..2
>     ok 33 - case 25: node tool.js -af # time=0.824ms
>     
>     # Subtest: case 26: node tool.js -af foo.txt
>         ok 1 - should be equivalent
>         1..1
>     ok 34 - case 26: node tool.js -af foo.txt # time=0.771ms
>     
>     # Subtest: case 27: node tool.js -affoo.txt
>         ok 1 - should be equivalent
>         1..1
>     ok 35 - case 27: node tool.js -affoo.txt # time=0.724ms
>     
>     # Subtest: case 28: node tool.js -v -vvf
>         ok 1 - error message did not match /do not have enough args/: "do not have enough args for "-f" option"
>         ok 2 - expected an error
>         1..2
>     ok 36 - case 28: node tool.js -v -vvf # time=5.803ms
>     
>     # Subtest: case 29: node tool.js -v -vvf foo.txt
>         ok 1 - should be equivalent
>         1..1
>     ok 37 - case 29: node tool.js -v -vvf foo.txt # time=0.803ms
>     
>     # Subtest: case 30: node tool.js -v -vvffoo.txt
>         ok 1 - should be equivalent
>         1..1
>     ok 38 - case 30: node tool.js -v -vvffoo.txt # time=0.741ms
>     
>     # Subtest: case 31: node tool.js -a 5 -b4 -c -1 -d -3.14159 -e 1.0e42 foo
>         ok 1 - should be equivalent
>         1..1
>     ok 39 - case 31: node tool.js -a 5 -b4 -c -1 -d -3.14159 -e 1.0e42 foo # time=1.101ms
>     
>     # Subtest: case 32: node tool.js -t 5a
>         ok 1 - error message did not match /arg for "-t" is not a number/: "arg for "-t" is not a number: "5a""
>         ok 2 - expected an error
>         1..2
>     ok 40 - case 32: node tool.js -t 5a # time=1.018ms
>     
>     # Subtest: case 33: node tool.js -vvv foo bar
>         ok 1 - should be equivalent
>         1..1
>     ok 41 - case 33: node tool.js -vvv foo bar # time=0.685ms
>     
>     # Subtest: case 34: node tool.js foo bar
>         ok 1 - should be equivalent
>         1..1
>     ok 42 - case 34: node tool.js foo bar # time=0.575ms
>     
>     # Subtest: case 35: node tool.js -w club --weapon mallet -w sword bang
>         ok 1 - should be equivalent
>         1..1
>     ok 43 - case 35: node tool.js -w club --weapon mallet -w sword bang # time=0.706ms
>     
>     # Subtest: case 36: node tool.js --split 10 -s 5 -s 0.01 bang
>         ok 1 - should be equivalent
>         1..1
>     ok 44 - case 36: node tool.js --split 10 -s 5 -s 0.01 bang # time=0.683ms
>     
>     # Subtest: case 37: node tool.js --help
>         ok 1 - help did not match /-h, --help\\s+Show help and exit./: "    -h, --help      Show help and exit. "
>         1..1
>     ok 45 - case 37: node tool.js --help # time=1.741ms
>     
>     # Subtest: case 38: node option-groups-tool.js --help
>         ok 1 - help did not match /--help\\n\\n\\s\\sfirst group:/m: "    -h, --help    first group:     -f, --first-one     -F, --first-two    second group:     -s, --second-one     -S, --second-two "
>         ok 2 - help did not match /^\\s\\sfirst group:\\n\\s\\s\\s\\s-f, --first-one$/m: "    -h, --help    first group:     -f, --first-one     -F, --first-two    second group:     -s, --second-one     -S, --second-two "
>         ok 3 - help did not match /first-two\\n\\n\\s\\ssecond group:\\n\\s\\s\\s\\s-s, --second-one$/m: "    -h, --help    first group:     -f, --first-one     -F, --first-two    second group:     -s, --second-one     -S, --second-two "
>         1..3
>     ok 46 - case 38: node option-groups-tool.js --help # time=1.19ms
>     
>     # Subtest: case 39: node tool.js -t 0
>         ok 1 - should be equivalent
>         1..1
>     ok 47 - case 39: node tool.js -t 0 # time=0.738ms
>     
>     # Subtest: case 40: node tool.js -t 42
>         ok 1 - should be equivalent
>         1..1
>     ok 48 - case 40: node tool.js -t 42 # time=0.621ms
>     
>     # Subtest: case 41: node tool.js -t42
>         ok 1 - should be equivalent
>         1..1
>     ok 49 - case 41: node tool.js -t42 # time=0.543ms
>     
>     # Subtest: case 42: node tool.js -t -5
>         ok 1 - should be equivalent
>         1..1
>     ok 50 - case 42: node tool.js -t -5 # time=0.56ms
>     
>     # Subtest: case 43: node tool.js -t-5
>         ok 1 - should be equivalent
>         1..1
>     ok 51 - case 43: node tool.js -t-5 # time=0.578ms
>     
>     # Subtest: case 44: node tool.js -t 1e2
>         ok 1 - error message did not match /arg for "-t" is not an integer/: "arg for "-t" is not an integer: "1e2""
>         ok 2 - expected an error
>         1..2
>     ok 52 - case 44: node tool.js -t 1e2 # time=0.521ms
>     
>     # Subtest: case 45: node tool.js -t 0x32
>         ok 1 - error message did not match /arg for "-t" is not an integer/: "arg for "-t" is not an integer: "0x32""
>         ok 2 - expected an error
>         1..2
>     ok 53 - case 45: node tool.js -t 0x32 # time=0.497ms
>     
>     # Subtest: case 46: node tool.js -t 3.1
>         ok 1 - error message did not match /arg for "-t" is not an integer/: "arg for "-t" is not an integer: "3.1""
>         ok 2 - expected an error
>         1..2
>     ok 54 - case 46: node tool.js -t 3.1 # time=0.481ms
>     
>     # Subtest: case 47: node tool.js -t 42.
>         ok 1 - error message did not match /arg for "-t" is not an integer/: "arg for "-t" is not an integer: "42.""
>         ok 2 - expected an error
>         1..2
>     ok 55 - case 47: node tool.js -t 42. # time=0.471ms
>     
>     # Subtest: case 48: node tool.js -t 1e-2
>         ok 1 - error message did not match /arg for "-t" is not an integer/: "arg for "-t" is not an integer: "1e-2""
>         ok 2 - expected an error
>         1..2
>     ok 56 - case 48: node tool.js -t 1e-2 # time=0.489ms
>     
>     # Subtest: case 49: node tool.js
>         ok 1 - should be equivalent
>         1..1
>     ok 57 - case 49: node tool.js # time=0.477ms
>     
>     # Subtest: case 50: node tool.js -t 42
>         ok 1 - should be equivalent
>         1..1
>     ok 58 - case 50: node tool.js -t 42 # time=0.549ms
>     
>     # Subtest: case 51: node tool.js -t 1 -t 2 -t -3
>         ok 1 - should be equivalent
>         1..1
>     ok 59 - case 51: node tool.js -t 1 -t 2 -t -3 # time=0.634ms
>     
>     # Subtest: case 52: node tool.js -t 1 -t 1e2
>         ok 1 - error message did not match /arg for "-t" is not an integer/: "arg for "-t" is not an integer: "1e2""
>         ok 2 - expected an error
>         1..2
>     ok 60 - case 52: node tool.js -t 1 -t 1e2 # time=0.491ms
>     
>     # Subtest: case 53: node tool.js -t 0
>         ok 1 - error message did not match /arg for "-t" is not a positive integer/: "arg for "-t" is not a positive integer: "0""
>         ok 2 - expected an error
>         1..2
>     ok 61 - case 53: node tool.js -t 0 # time=0.737ms
>     
>     # Subtest: case 54: node tool.js -t 42
>         ok 1 - should be equivalent
>         1..1
>     ok 62 - case 54: node tool.js -t 42 # time=0.636ms
>     
>     # Subtest: case 55: node tool.js -t42
>         ok 1 - should be equivalent
>         1..1
>     ok 63 - case 55: node tool.js -t42 # time=0.523ms
>     
>     # Subtest: case 56: node tool.js -t -5
>         ok 1 - error message did not match /arg for "-t" is not a positive integer/: "arg for "-t" is not a positive integer: "-5""
>         ok 2 - expected an error
>         1..2
>     ok 64 - case 56: node tool.js -t -5 # time=0.484ms
>     
>     # Subtest: case 57: node tool.js -t42
>         ok 1 - should be equivalent
>         1..1
>     ok 65 - case 57: node tool.js -t42 # time=0.599ms
>     
>     # Subtest: case 58: node tool.js -t 42 -t -5
>         ok 1 - error message did not match /arg for "-t" is not a positive integer/: "arg for "-t" is not a positive integer: "-5""
>         ok 2 - expected an error
>         1..2
>     ok 66 - case 58: node tool.js -t 42 -t -5 # time=0.548ms
>     
>     # Subtest: case 59: node foo.js -v
>         ok 1 - should be equivalent
>         1..1
>     ok 67 - case 59: node foo.js -v # time=1.002ms
>     
>     # Subtest: case 60: FOO_VERBOSE=1 node foo.js -v
>         ok 1 - should be equivalent
>         1..1
>     ok 68 - case 60: FOO_VERBOSE=1 node foo.js -v # time=0.648ms
>     
>     # Subtest: case 61: FOO_VERBOSE=1 node foo.js
>         ok 1 - should be equivalent
>         1..1
>     ok 69 - case 61: FOO_VERBOSE=1 node foo.js # time=0.783ms
>     
>     # Subtest: case 62: FOO_VERBOSE=0 node foo.js
>         ok 1 - should be equivalent
>         1..1
>     ok 70 - case 62: FOO_VERBOSE=0 node foo.js # time=0.697ms
>     
>     # Subtest: case 63: FOO_VERBOSE= node foo.js
>         ok 1 - should be equivalent
>         1..1
>     ok 71 - case 63: FOO_VERBOSE= node foo.js # time=0.543ms
>     
>     # Subtest: case 64: node tool.js --help
>         ok 1 - help did not match /-a ARG\\s+Phrase. Environment: A=ARG/: "    -a ARG          Phrase. Environment: A=ARG     -b ARG          Sentence. Environment: B=ARG     -c ARG          Question? Environment: C=ARG     -d ARG          Exclamation! Environment: D=ARG     -e ARG          Environment: E=ARG     -f ARG          Environment: F=ARG     -g ARG          Environment: G=ARG     -h              Environment: H=1 "
>         ok 2 - help did not match /-b ARG\\s+Sentence. Environment: B=ARG/: "    -a ARG          Phrase. Environment: A=ARG     -b ARG          Sentence. Environment: B=ARG     -c ARG          Question? Environment: C=ARG     -d ARG          Exclamation! Environment: D=ARG     -e ARG          Environment: E=ARG     -f ARG          Environment: F=ARG     -g ARG          Environment: G=ARG     -h              Environment: H=1 "
>         ok 3 - help did not match /-c ARG\\s+Question\\? Environment: C=ARG/: "    -a ARG          Phrase. Environment: A=ARG     -b ARG          Sentence. Environment: B=ARG     -c ARG          Question? Environment: C=ARG     -d ARG          Exclamation! Environment: D=ARG     -e ARG          Environment: E=ARG     -f ARG          Environment: F=ARG     -g ARG          Environment: G=ARG     -h              Environment: H=1 "
>         ok 4 - help did not match /-d ARG\\s+Exclamation! Environment: D=ARG/: "    -a ARG          Phrase. Environment: A=ARG     -b ARG          Sentence. Environment: B=ARG     -c ARG          Question? Environment: C=ARG     -d ARG          Exclamation! Environment: D=ARG     -e ARG          Environment: E=ARG     -f ARG          Environment: F=ARG     -g ARG          Environment: G=ARG     -h              Environment: H=1 "
>         ok 5 - help did not match /-e ARG\\s+Environment: E=ARG/: "    -a ARG          Phrase. Environment: A=ARG     -b ARG          Sentence. Environment: B=ARG     -c ARG          Question? Environment: C=ARG     -d ARG          Exclamation! Environment: D=ARG     -e ARG          Environment: E=ARG     -f ARG          Environment: F=ARG     -g ARG          Environment: G=ARG     -h              Environment: H=1 "
>         ok 6 - help did not match /-f ARG\\s+Environment: F=ARG/: "    -a ARG          Phrase. Environment: A=ARG     -b ARG          Sentence. Environment: B=ARG     -c ARG          Question? Environment: C=ARG     -d ARG          Exclamation! Environment: D=ARG     -e ARG          Environment: E=ARG     -f ARG          Environment: F=ARG     -g ARG          Environment: G=ARG     -h              Environment: H=1 "
>         ok 7 - help did not match /-g ARG\\s+Environment: G=ARG/: "    -a ARG          Phrase. Environment: A=ARG     -b ARG          Sentence. Environment: B=ARG     -c ARG          Question? Environment: C=ARG     -d ARG          Exclamation! Environment: D=ARG     -e ARG          Environment: E=ARG     -f ARG          Environment: F=ARG     -g ARG          Environment: G=ARG     -h              Environment: H=1 "
>         ok 8 - help did not match /-h\\s+Environment: H=1/: "    -a ARG          Phrase. Environment: A=ARG     -b ARG          Sentence. Environment: B=ARG     -c ARG          Question? Environment: C=ARG     -d ARG          Exclamation! Environment: D=ARG     -e ARG          Environment: E=ARG     -f ARG          Environment: F=ARG     -g ARG          Environment: G=ARG     -h              Environment: H=1 "
>         1..8
>     ok 72 - case 64: node tool.js --help # time=2.354ms
>     
>     # Subtest: case 65: node foo.js -t 42
>         ok 1 - should be equivalent
>         1..1
>     ok 73 - case 65: node foo.js -t 42 # time=0.602ms
>     
>     # Subtest: case 66: FOO_TIMEOUT=32 node foo.js
>         ok 1 - should be equivalent
>         1..1
>     ok 74 - case 66: FOO_TIMEOUT=32 node foo.js # time=0.542ms
>     
>     # Subtest: case 67: FOO_TIMEOUT=32 node foo.js -t 52
>         ok 1 - should be equivalent
>         1..1
>     ok 75 - case 67: FOO_TIMEOUT=32 node foo.js -t 52 # time=0.543ms
>     
>     # Subtest: case 68: FOO_TIMEOUT=wallawalla node foo.js -t 52
>         ok 1 - should be equivalent
>         1..1
>     ok 76 - case 68: FOO_TIMEOUT=wallawalla node foo.js -t 52 # time=0.529ms
>     
>     # Subtest: case 69: FOO_TIMEOUT=wallawalla node foo.js
>         ok 1 - error message did not match /arg for "FOO_TIMEOUT" is not a number: "wallawalla"/: "arg for "FOO_TIMEOUT" is not a number: "wallawalla""
>         ok 2 - expected an error
>         1..2
>     ok 77 - case 69: FOO_TIMEOUT=wallawalla node foo.js # time=0.509ms
>     
>     # Subtest: case 70: FOO_VERBOSE=blah node foo.js
>         ok 1 - should be equivalent
>         1..1
>     ok 78 - case 70: FOO_VERBOSE=blah node foo.js # time=0.589ms
>     
>     # Subtest: case 71: FOO_VERBOSE=blah node foo.js -v
>         ok 1 - should be equivalent
>         1..1
>     ok 79 - case 71: FOO_VERBOSE=blah node foo.js -v # time=0.539ms
>     
>     # Subtest: case 72: FOO_VERBOSE=blah node foo.js -vv
>         ok 1 - should be equivalent
>         1..1
>     ok 80 - case 72: FOO_VERBOSE=blah node foo.js -vv # time=0.57ms
>     
>     # Subtest: case 73: node foo.js --dry-run
>         ok 1 - should be equivalent
>         1..1
>     ok 81 - case 73: node foo.js --dry-run # time=0.535ms
>     
>     # Subtest: case 74: node foo.js --foo-bar-
>         ok 1 - should be equivalent
>         1..1
>     ok 82 - case 74: node foo.js --foo-bar- # time=0.576ms
>     
>     # Subtest: case 75: node foo.js
>         ok 1 - should be equivalent
>         1..1
>     ok 83 - case 75: node foo.js # time=0.554ms
>     
>     # Subtest: case 76: FOO_FILE=env.file node foo.js
>         ok 1 - should be equivalent
>         1..1
>     ok 84 - case 76: FOO_FILE=env.file node foo.js # time=0.532ms
>     
>     # Subtest: case 77: FOO_FILE=env.file node foo.js -f argv.file
>         ok 1 - should be equivalent
>         1..1
>     ok 85 - case 77: FOO_FILE=env.file node foo.js -f argv.file # time=0.511ms
>     
>     # Subtest: case 78: node foo.js
>         ok 1 - should be equivalent
>         1..1
>     ok 86 - case 78: node foo.js # time=0.513ms
>     
>     # Subtest: case 79: FOO_VERBOSE=1 node foo.js
>         ok 1 - should be equivalent
>         1..1
>     ok 87 - case 79: FOO_VERBOSE=1 node foo.js # time=0.53ms
>     
>     # Subtest: case 80: FOO_VERBOSE=0 node foo.js
>         ok 1 - should be equivalent
>         1..1
>     ok 88 - case 80: FOO_VERBOSE=0 node foo.js # time=0.636ms
>     
>     # Subtest: case 81: FOO_VERBOSE=0 node foo.js -v
>         ok 1 - should be equivalent
>         1..1
>     ok 89 - case 81: FOO_VERBOSE=0 node foo.js -v # time=0.509ms
>     
>     # Subtest: case 82: node tool.js a --help -b --cheese
>         ok 1 - should be equivalent
>         1..1
>     ok 90 - case 82: node tool.js a --help -b --cheese # time=0.637ms
>     
>     # Subtest: case 83: node tool.js a -bcd --cheese --help
>         ok 1 - should be equivalent
>         1..1
>     ok 91 - case 83: node tool.js a -bcd --cheese --help # time=0.613ms
>     
>     # Subtest: case 84: node foo.js -s
>         ok 1 - error message did not match /do not have enough args for "-s" option/: "do not have enough args for "-s" option"
>         ok 2 - expected an error
>         1..2
>     ok 92 - case 84: node foo.js -s # time=0.534ms
>     
>     # Subtest: case 85: node foo.js -s notadate
>         ok 1 - error message did not match /arg for "-s" is not a valid date format: "notadate"/: "arg for "-s" is not a valid date format: "notadate""
>         ok 2 - expected an error
>         1..2
>     ok 93 - case 85: node foo.js -s notadate # time=0.837ms
>     
>     # Subtest: case 86: node foo.js -s 0
>         ok 1 - should be equivalent
>         1..1
>     ok 94 - case 86: node foo.js -s 0 # time=0.849ms
>     
>     # Subtest: case 87: node foo.js -s 1
>         ok 1 - should be equivalent
>         1..1
>     ok 95 - case 87: node foo.js -s 1 # time=0.535ms
>     
>     # Subtest: case 88: node foo.js -s 1396065084
>         ok 1 - should be equivalent
>         1..1
>     ok 96 - case 88: node foo.js -s 1396065084 # time=0.536ms
>     
>     # Subtest: case 89: node foo.js -s 2014-04-01
>         ok 1 - should be equivalent
>         1..1
>     ok 97 - case 89: node foo.js -s 2014-04-01 # time=0.758ms
>     
>     # Subtest: case 90: node foo.js -s 2014-04-01T
>         ok 1 - error message did not match /arg for "-s" is not a valid date format: "2014-04-01T"/: "arg for "-s" is not a valid date format: "2014-04-01T""
>         ok 2 - expected an error
>         1..2
>     ok 98 - case 90: node foo.js -s 2014-04-01T # time=0.508ms
>     
>     # Subtest: case 91: node foo.js -s 2014-04-01T12:01:02
>         ok 1 - should be equivalent
>         1..1
>     ok 99 - case 91: node foo.js -s 2014-04-01T12:01:02 # time=0.535ms
>     
>     # Subtest: case 92: node foo.js -s 2014-04-01T12:01:02Z
>         ok 1 - should be equivalent
>         1..1
>     ok 100 - case 92: node foo.js -s 2014-04-01T12:01:02Z # time=0.736ms
>     
>     # Subtest: case 93: node foo.js -s 2014-04-01T12:01:02.7
>         ok 1 - should be equivalent
>         1..1
>     ok 101 - case 93: node foo.js -s 2014-04-01T12:01:02.7 # time=0.744ms
>     
>     # Subtest: case 94: node foo.js -s 2014-04-01T12:01:02.456Z
>         ok 1 - should be equivalent
>         1..1
>     ok 102 - case 94: node foo.js -s 2014-04-01T12:01:02.456Z # time=0.689ms
>     
>     # Subtest: case 95: node foo.js -s 2014-04-01t12:01:02.456z
>         ok 1 - should be equivalent
>         1..1
>     ok 103 - case 95: node foo.js -s 2014-04-01t12:01:02.456z # time=1.77ms
>     
>     # Subtest: case 96: node foo.js --times 1 -t 2 -t 2014-04-01
>         ok 1 - should be equivalent
>         1..1
>     ok 104 - case 96: node foo.js --times 1 -t 2 -t 2014-04-01 # time=2.113ms
>     
>     # Subtest: case 97: node foo.js -a yes
>         ok 1 - should be equivalent
>         1..1
>     ok 105 - case 97: node foo.js -a yes # time=1.504ms
>     
>     # Subtest: case 98: node foo.js -a no
>         ok 1 - should be equivalent
>         1..1
>     ok 106 - case 98: node foo.js -a no # time=1.541ms
>     
>     # Subtest: case 99: node helpWrapTool.js --help
>         ok 1 - help did not match /long help with newlines spaces and such will not render/: "    -o ARG, --opt=ARG    long help with newlines spaces and such will not render                          correctly. Environment: ENVVARIABLE=ARG     -a ARG, --array=ARG  long help with                            newlines                            spaces                            and such                          will render correctly                          Environment: OTHERVARIABLE=ARG     --foo=ARG            Environment: FOOVAR=ARG "
>         ok 2 - help did not match /\\. Environment: ENVVARIABLE=ARG/: "    -o ARG, --opt=ARG    long help with newlines spaces and such will not render                          correctly. Environment: ENVVARIABLE=ARG     -a ARG, --array=ARG  long help with                            newlines                            spaces                            and such                          will render correctly                          Environment: OTHERVARIABLE=ARG     --foo=ARG            Environment: FOOVAR=ARG "
>         ok 3 - help did not match /long help with$/m: "    -o ARG, --opt=ARG    long help with newlines spaces and such will not render                          correctly. Environment: ENVVARIABLE=ARG     -a ARG, --array=ARG  long help with                            newlines                            spaces                            and such                          will render correctly                          Environment: OTHERVARIABLE=ARG     --foo=ARG            Environment: FOOVAR=ARG "
>         ok 4 - help did not match /^ +newlines$/m: "    -o ARG, --opt=ARG    long help with newlines spaces and such will not render                          correctly. Environment: ENVVARIABLE=ARG     -a ARG, --array=ARG  long help with                            newlines                            spaces                            and such                          will render correctly                          Environment: OTHERVARIABLE=ARG     --foo=ARG            Environment: FOOVAR=ARG "
>         ok 5 - help did not match /^ +Environment: OTHERVARIABLE=ARG/m: "    -o ARG, --opt=ARG    long help with newlines spaces and such will not render                          correctly. Environment: ENVVARIABLE=ARG     -a ARG, --array=ARG  long help with                            newlines                            spaces                            and such                          will render correctly                          Environment: OTHERVARIABLE=ARG     --foo=ARG            Environment: FOOVAR=ARG "
>         ok 6 - help did not match /^ +--foo=ARG +Environment: FOOVAR=ARG$/m: "    -o ARG, --opt=ARG    long help with newlines spaces and such will not render                          correctly. Environment: ENVVARIABLE=ARG     -a ARG, --array=ARG  long help with                            newlines                            spaces                            and such                          will render correctly                          Environment: OTHERVARIABLE=ARG     --foo=ARG            Environment: FOOVAR=ARG "
>         1..6
>     ok 107 - case 99: node helpWrapTool.js --help # time=3.562ms
>     
>     # Subtest: case 100: node helpWrapTool2.js --help
>         ok 1 - help did not match /long help with$/m: "    -a ARG, --array=ARG  long help with                            newlines                            spaces                            and such                          will render correctly                          Environment: OTHERVARIABLE=ARG "
>         ok 2 - help did not match /^ +newlines$/m: "    -a ARG, --array=ARG  long help with                            newlines                            spaces                            and such                          will render correctly                          Environment: OTHERVARIABLE=ARG "
>         ok 3 - help did not match /^ +Environment: OTHERVARIABLE=ARG/m: "    -a ARG, --array=ARG  long help with                            newlines                            spaces                            and such                          will render correctly                          Environment: OTHERVARIABLE=ARG "
>         1..3
>     ok 108 - case 100: node helpWrapTool2.js --help # time=1.445ms
>     
>     # Subtest: case 101: node hidden-opts.js --help
>         ok 1 - help did not match /-h, --help\\n\\s+--version/m: "    -h, --help     --version "
>         1..1
>     ok 109 - case 101: node hidden-opts.js --help # time=0.691ms
>     
>     # Subtest: case 102: node foo.js
>         ok 1 - should be equivalent
>         1..1
>     ok 110 - case 102: node foo.js # time=1.469ms
>     
>     # Subtest: case 103: node foo.js -p pear
>         ok 1 - should be equivalent
>         ok 2 - help did not match /^ {2}Filling:$/m: "  Filling:     -p <fruit>, --pie=<fruit>  Environment: FRUIT=<fruit>. Default: "apple" "
>         ok 3 - help did not match / +Environment: FRUIT=<fruit>\\. Default: "apple"/m: "  Filling:     -p <fruit>, --pie=<fruit>  Environment: FRUIT=<fruit>. Default: "apple" "
>         1..3
>     ok 111 - case 103: node foo.js -p pear # time=2.375ms
>     
>     # Subtest: case 104: node foo.js -m a,b -m c,d,,
>         ok 1 - should be equivalent
>         1..1
>     ok 112 - case 104: node foo.js -m a,b -m c,d,, # time=1.194ms
>     
>     1..112
>     # time=322.339ms
> }
> 
> 1..1
> # time=1595.321ms
> ERROR: Coverage for lines (81.73%) does not meet global threshold (100%)
> ERROR: Coverage for functions (81.39%) does not meet global threshold (100%)
> ERROR: Coverage for branches (75.08%) does not meet global threshold (100%)
> ERROR: Coverage for statements (81.9%) does not meet global threshold (100%)
> -------------|---------|----------|---------|---------|---------------------------------------------
> File         | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s                           
> -------------|---------|----------|---------|---------|---------------------------------------------
> All files    |    81.9 |    75.08 |   81.39 |   81.73 |                                             
>  dashdash.js |    81.9 |    75.08 |   81.39 |   81.73 | ...674,715,727,744,791,824-829,876-994,1084 
> -------------|---------|----------|---------|---------|---------------------------------------------
> 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-dashdash_2.0.0-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