Your message dated Thu, 14 Apr 2022 13:49:06 +0000
with message-id <e1nezqm-0008al...@fasolo.debian.org>
and subject line Bug#1009547: fixed in node-stream-browserify 3.0.0-2
has caused the Debian Bug report #1009547,
regarding node-stream-browserify: FTBFS: ERROR: Coverage for statements
(24.07%) does not meet global threshold (100%)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1009547: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009547
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-stream-browserify
Version: 3.0.0-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
> 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/stream-browserify
> /bin/sh -ex debian/tests/pkg-js/test
> + tap -R spec test/buf.js test/index.js test/pipeline.js test/use-stream.js
>
> test/buf.js
>
> ✓ should be strictly equal
>
> ✓ should be strictly equal
> test/index.js
>
> ✓ should be strictly equal
>
> ✓ should be strictly equal
>
> ✓ transform2.close called
>
> ✓ writable.close called
>
> ✓ should be truthy
>
> ✓ should be strictly equal
> test/pipeline.js
>
> ✓ transform2.close called
>
> ✓ writable.close called
>
> ✓ should be truthy
>
> ✓ should be strictly equal
> test/use-stream.js
> - test/use-stream.js
>
> 12 passing (921.361ms)
> 1 pending
> ERROR: Coverage for lines (25.49%) does not meet global threshold (100%)
> ERROR: Coverage for functions (0%) does not meet global threshold (100%)
> ERROR: Coverage for branches (0%) does not meet global threshold (100%)
> ERROR: Coverage for statements (24.07%) does not meet global threshold (100%)
> ----------|---------|----------|---------|---------|-------------------
> File | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s
> ----------|---------|----------|---------|---------|-------------------
> All files | 24.07 | 0 | 0 | 25.49 |
> index.js | 24.07 | 0 | 0 | 25.49 | 45,49-128
> ----------|---------|----------|---------|---------|-------------------
> 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-stream-browserify_3.0.0-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.
--- End Message ---
--- Begin Message ---
Source: node-stream-browserify
Source-Version: 3.0.0-2
Done: Yadd <y...@debian.org>
We believe that the bug you reported is fixed in the latest version of
node-stream-browserify, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1009...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Yadd <y...@debian.org> (supplier of updated node-stream-browserify package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Thu, 14 Apr 2022 15:32:56 +0200
Source: node-stream-browserify
Architecture: source
Version: 3.0.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers
<pkg-javascript-de...@lists.alioth.debian.org>
Changed-By: Yadd <y...@debian.org>
Closes: 1009547
Changes:
node-stream-browserify (3.0.0-2) unstable; urgency=medium
.
* Team upload
* Fix test for tap >= 15 (--no-cov) (Closes: #1009547)
Checksums-Sha1:
8151eff3fe74959434b5c5b098fca9e856034b95 2247
node-stream-browserify_3.0.0-2.dsc
a5df576980fe4cd4112672b14f846fe750f98700 3504
node-stream-browserify_3.0.0-2.debian.tar.xz
Checksums-Sha256:
cc94926f17235c0c9144b3c5fe357674a0cbe8cfe589367ff3d46af78ae2d1c6 2247
node-stream-browserify_3.0.0-2.dsc
ed98f20c81ea735f8b31aa0c73eb8cd8a033b86370fae2217801db6a8c84f743 3504
node-stream-browserify_3.0.0-2.debian.tar.xz
Files:
9f7714424c0d63f89b32cfc0aad5bae9 2247 javascript optional
node-stream-browserify_3.0.0-2.dsc
1526296c4818dfef8fdadcf654e78f12 3504 javascript optional
node-stream-browserify_3.0.0-2.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmJYIssACgkQ9tdMp8mZ
7ukPyQ//eVn0SBiQ0T6XCSleq4u66rhNgG8N9gEnsW8H0p9ksSf68FmYFoALhArx
+E+3WTHKbDQS3gsOCaFHDmF/u+VlR9lI+5Ai/RfO2RjVNJkX4dJ0SGGSHtVdzJVb
kQHIVGrMgPko2TvIadSKadMfKyE/EwmM8Ug+/e3nKjJ71jFv5FtweynbEw4aV2wD
oYH4fyPZESDX+epaFHP1Xhqpgkq8lJ2grbeNSk2SBCVbgaTB/GgOADFNTv2Z4dvp
eeBRvk/6/JMVXR/8MOmsu5vJkCMElboghhOtVPXX3sIvtzF7qzjmV0C79ENEFRBE
1QV4+bAistdU8Z/EWXgH6vImxNVT142lmjcdJnj8uUcdF9UzMND+OL7j+pl+MpPV
XSuRV6FN2vw8GnMZ2L3J+mL8ZU97o7uJ9BNvUCv/JqkVkW5VYtycjw8DakSlZINM
0eBGamIqlnTsxx1FQNPAguzXAYAda1Z1BS2qeWgfKBmhH0f0p3Jq2QvPz6Ivdli3
EdqEgfXXLZN8fwdcxc4nkZdDyaTno7BRV8X20FzhKtaxWjMnAoCvwZRL+WYjGiJV
QqwQVwDRt+oeHKl/aNiRcI90Gcf0Go9FMHYG2iJoLbVHXz7Yn6c2jE5Wl3EAiOqc
RdJVrKm/axm/6BDNOse2K/IEz/+jeu2JjVwPeR3TjW+KPPZSIBA=
=atTt
-----END PGP SIGNATURE-----
--- End Message ---
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
