Bug#1009385: libldns3 1.7.1-2.1 changes output of ldns-key2ds, causing FTBFS on dns-root-data [was: Re: Bug#1009385: dns-root-data: FTBFS: root-anchors.ds root.ds differ]

[Daniel Kahn Gillmor]

Control: reassign 1009385 libldns3 1.7.1-2.1
Control: retitle 1009385 libldns3 1.7.1-2.1 changes output of ldns-key2ds, 
causing FTBFS on dns-root-data
Control: affects 1009385 + dns-root-data
X-Debbugs-Cc: Michael Tokarev 
Control: tags 1009385 + help

Lucas, thanks for flagging this!

The build failure below appears to happen when libldns3 1.7.1-2.1 is
installed.

It does not fail with libldns3 1.7.1-2+b1.  The output of ldns-key2ds
has changed between these two versions.  yikes!

Michael, it looks like it was this particular upload for ldns:

-
ldns (1.7.1-2.1) unstable; urgency=medium

  * Non-maintainer upload.
  * add fix-wrong-python-distutils-configure-check.diff to fix the
incorrect distutils package check (it should be checking the
return code not the emptiness of the output). This fixes FTBFS
with new python (3.10) and allows the python3.10 transition to
happen, but it is not fixing the actual issiue with ldns using
distutils which should be addressed later.  Closes: #1008638

 -- Michael Tokarev   Thu, 07 Apr 2022 16:03:29 +0300
-

This doesn't seem like it should be a relevant change to adjust the
output of /usr/bin/ldns-key2ds, but it does:

here's a narrow transcript that shows what should be a deterministic
result varying depending on the version:

0 dkg@alice:~/src/pkg-dns/dns-root-data$ dpkg -l libldns3
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version  Architecture Description
+++-==---=
ii  libldns3:amd64 1.7.1-2+b1   amd64ldns library for DNS programming
0 dkg@alice:~/src/pkg-dns/dns-root-data$ /usr/bin/ldns-key2ds -n -2 root.key 
.   86400   IN  DS  20326 8 2 
e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
0 dkg@alice:~/src/pkg-dns/dns-root-data$ dpkg -l libldns3
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version  Architecture Description
+++-==---=
ii  libldns3:amd64 1.7.1-2.1amd64ldns library for DNS programming
0 dkg@alice:~/src/pkg-dns/dns-root-data$ /usr/bin/ldns-key2ds -n -2 root.key 
.   86400   IN  DS  20326 8 2 
0ae721f59a19244008217c3d2a646183acef2f17cf4c30929a3f29d09311c05e
0 dkg@alice:~/src/pkg-dns/dns-root-data$ 


Any idea what's happened here?

--dkg

On Tue 2022-04-12 20:38:47 +0200, Lucas Nussbaum wrote:
> Source: dns-root-data
> Version: 2021011101
> 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):
>> make[1]: Entering directory '/<>'
>> # Verify root-anchors.xml using OpenSSL
>> openssl smime -verify -noverify -inform DER -in root-anchors.p7s -content 
>> root-anchors.xml
>> Verification successful
>> 
>> > source="http://data.iana.org/root-anchors/root-anchors.xml";>
>> .
>> > validUntil="2019-01-11T00:00:00+00:00">
>> 19036
>> 8
>> 2
>> 49AAC11D7B6F6446702E54A1607371607A1A41855200FD2CE1CDDE32F24E8FB5
>> 
>> 
>> 20326
>> 8
>> 2
>> E06D44B80B8F1D39A95C0B0D7C65D08458E880409BBC683457104237C7F8EC8D
>> 
>> 
>> # Verify root.hints
>> gpgv --keyring /<>/registry-admin.key 
>> /<>/root.hints.sig /<>/root.hints
>> gpgv: Signature made Mon Jan 11 15:55:50 2021 UTC
>> gpgv:using DSA key 937BB869E3A238C5
>> gpgv: Good signature from "Registry Administrator "
>> # Create key from validated root-anchors.xml
>> ./parse-root-anchors.sh < root-anchors.xml | sort -k 4 -n > root-anchors.ds
>> Digest 49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5 
>> expired on 2019-01-11T00:00:00+00:00
>> # Create key from downloaded root.key
>> /usr/bin/ldns-key2ds -n -2 root.key | cut --fields=1,3- --output-delimiter=' 
>> ' | sort -k 4 -n > root.ds
>> # Compare the DS from root.key and from root-anchors.xml
>> diff -u root-anchors.ds root.ds
>> --- root-anchors.ds  2022-04-12 16:59:11.126351522 +
>> +++ root.ds  2022-04-12 16:59:11.130351536 +
>> @@ -1 +1 @@
>> -. IN DS 20326 8 2 
>> e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
>> +. IN DS 20326 8 2 
>> 0ae7

Bug#1009417: saga: FTBFS: configure: error: cannot import Python module "distutils".

[Johan Van de Wauw]

I will check.

The mRMR issue has been addressed. I will target a new release (and change
the build system to cmake, as autotools will be deprecated next release).

On Tue, Apr 12, 2022 at 10:55 PM Sebastiaan Couwenberg 
wrote:

> On 4/12/22 20:23, Lucas Nussbaum wrote:
> >> checking for python script directory (pythondir)...
> ${PYTHON_PREFIX}/lib/python3.10/site-packages
> >> checking for python extension module directory (pyexecdir)...
> ${PYTHON_EXEC_PREFIX}/lib/python3.10/site-packages
> >> checking for python3.10... (cached) /usr/bin/python3
> >> checking for a version of Python >= '2.1.0'... yes
> >> checking for the distutils Python package... no
> >> configure: error: cannot import Python module "distutils".
> >> Please check your Python installation. The error was:
> >> :1: DeprecationWarning: The distutils package is deprecated and
> slated for removal in Python 3.12. Use setuptools or check PEP 632 for
> potential alternatives
>
> Johan can you fix this (upstream)?
>
> And has the mRMR license issue been addressed upstream to unblock
> updating the package to 8.x?
>
> Kind Regards,
>
> Bas
>
> --
>   GPG Key ID: 4096R/6750F10AE88D4AF1
> Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1
>

Bug#991533: lintian: please forget about required-field Standards-Version for udeb packages

[Cyril Brulebois]

Hi,

Sean Whitton  (2021-08-12):
> On Tue 27 Jul 2021 at 04:08AM +02, Cyril Brulebois wrote:
> 
> > Whatever happens on the debian-policy front (if anything), I'd prefer if
> > lintian would stop emitting those errors on its own. It doesn't have to
> > follow the letter of Policy, does it?
> 
> No, it doesn't.  While the Lintian maintainers could decide to change
> that, it's not been how the project has viewed Lintian in the past.

Thanks Sean for the confirmation.

Lintian maintainers, can we please drop this? It's annoying and
distracting to see those errors/warnings all the time when working on
the installer.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#1009622: ck: FTBFS on armhf due to wrong -march target

[Steve Langasek]

Package: ck
Version: 0.7.1-6
Severity: important
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu jammy ubuntu-patch

Hi Daniel,

In Ubuntu, ck fails to build on armhf because the upstream build system is
passing an explicit -march option that is no longer correct because it does
not include floating-point support which is implicit in armhf:

[...]
/usr/bin/cc -D_XOPEN_SOURCE=600 -D_BSD_SOURCE -D_DEFAULT_SOURCE -std=gnu99 
-pedantic -Wall -W -Wundef -Wendif-labels -Wshadow -Wpointer-arith -Wcast-align 
-Wcast-qual -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes 
-Wnested-externs -Winline -Wdisabled-optimization -fstrict-aliasing -O2 -pipe 
-Wno-parentheses -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -march=armv7-a -fPIC 
-D_XOPEN_SOURCE=600 -D_BSD_SOURCE -D_DEFAULT_SOURCE -std=gnu99 -pedantic -Wall 
-W -Wundef -Wendif-labels -Wshadow -Wpointer-arith -Wcast-align -Wcast-qual 
-Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wnested-externs 
-Winline -Wdisabled-optimization -fstrict-aliasing -O2 -pipe -Wno-parentheses 
-g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -march=armv7-a -fPIC -I/<>/include 
-I/<>/include -D__arm__ -c -o 
/<>/src/ck_barrier_tournament.o 
/<>/src/ck_barrier_tournament.c
cc1: error: ‘-mfloat-abi=hard’: selected architecture lacks an FPU
cc1: error: ‘-mfloat-abi=hard’: selected architecture lacks an FPU
[...]

  (https://launchpad.net/ubuntu/+source/ck/0.7.1-6/+build/22357550)

I have not verified whether this build failure exists with the current
toolchain in Debian, therefore I am not marking this as a serious bug;
however, I expect that if this toolchain change has not yet happened in
Debian, it will happen soon.

I have applied the attached patch in Ubuntu to let ck build by choosing an
appropriate cpu target of -march=armv7-a+fp.  Please consider applying it in
Debian as well.  Alternatively, upstream could just not override the -march
at all and trust the compiler defaults.

Thanks,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru ck-0.7.1/debian/rules ck-0.7.1/debian/rules
--- ck-0.7.1/debian/rules   2021-10-30 17:45:35.0 -0700
+++ ck-0.7.1/debian/rules   2022-04-12 23:30:57.0 -0700
@@ -2,6 +2,11 @@
 
 include /usr/share/dpkg/architecture.mk
 
+ifeq ($(DEB_HOST_ARCH),armhf)
+DEB_CFLAGS_MAINT_APPEND = -march=armv7-a+fp
+endif
+export DEB_CFLAGS_MAINT_APPEND
+
 ifneq (,$(filter $(DEB_HOST_ARCH), armel x32))
PLATFORM = --platform=unknown
 endif

Bug#1009621: ITP: python-sasl -- Python bindings for Cyrus libsasl2

[Daniel Kahn Gillmor]

Package: wnpp
Severity: wishlist
Owner: Daniel Kahn Gillmor 
X-Debbugs-Cc: debian-de...@lists.debian.org, d...@fifthhorseman.net

* Package name: python-sasl
  Version : 0.3.1
  Upstream Author : Todd Lipcon 
* URL : https://github.com/cloudera/python-sasl
* License : Apache-2.0
  Programming Lang: C, Python
  Description : Python bindings for libsasl2

This package should enable a Python-based tool to take advantage of
any installed SASL module.

This should be useful for testing tools like sasl-xoauth2 (see for
example #1006888)

Bug#1009309: udhcpc: allow usage without busybox

[Michael Tokarev]

11.04.2022 15:21, Helmut Grohne wrote:

Source: busybox
Version: 1:1.30.1-7
Severity: wishlist
Tags: patch

Hi Aurelien,

would it be possible to avoid the udhcpc -> busybox dependency? It may
seem strange to remove busybox in a quest to reduce file system usage at
first, but if you need iproute2 for other reasons, it should be fine at
providing what udhcpc needs. I'm attaching a patch so you can judge the
impact.


Helmut, I'm not sure I follow you here. udhcpc itself is provided by
bysybox. There's no udhcpc without busybox. udhcpc package is just a
set of support files for busybox's udhcpc applet. This is exactly why
I implemented it this way in the dhcp script: we're absolutely sure
busybox implementations of awk and ip are always here, since without
these there would be udhcpc.


If that's not a reasonable move forward, how about demoting the
dependency to Recommends? Admittedly, the case of using udhcpc without


No, as far as I understand. B/c udhcpc package lacks the main binary
if there's no busybox... ;)

Can you explain please? :)

/mjt

Bug#1009167: xz-utils: diff for NMU version 5.2.5-2.1

[Salvatore Bonaccorso]

Hi Jonathan,

On Tue, Apr 12, 2022 at 10:37:32PM -0700, Jonathan Nieder wrote:
> Hi Salvatore,
> 
> Salvatore Bonaccorso wrote:
> > On Sun, Apr 10, 2022 at 03:08:12PM +0200, Salvatore Bonaccorso wrote:
> 
> >> I've prepared an NMU for xz-utils (versioned as 5.2.5-2.1) and
> >> uploaded it to DELAYED/2. Please feel free to tell me if I
> >> should delay it longer.
> >
> > I noted that the last uploads done by Sebastian were NMUs, so hope it
> > is uncontroversial that I rescheduled the fix to delayed/0 and direct
> > upload tonight. There is not particular reason for the urgency, it's
> > more that I would like to base the bullseye-security just on top of
> > the 5.2.5-2.1 versioned 5.2.5-2.1~deb11u1 and have additionally the
> > fix first exposed in unstable enough as well for regression testing.
> 
> No problem at all.  Thanks for your work!  (And I'd be happy to have
> a new maintainer or co-maintainer if you're interested. :))

Thank you Jonathan! For co-maintenace: I think I have to happily
decline because I think I have already enough on my plate.

FWIW, status update: have preapred as well corresponding security
updates and we have scheduled for safety some regression testing as
well. We plan to release the DSA in the next few days (similarly for
gzip).

Regards,
Salvatore

Bug#1009167: xz-utils: diff for NMU version 5.2.5-2.1

[Jonathan Nieder]

Hi Salvatore,

Salvatore Bonaccorso wrote:
> On Sun, Apr 10, 2022 at 03:08:12PM +0200, Salvatore Bonaccorso wrote:

>> I've prepared an NMU for xz-utils (versioned as 5.2.5-2.1) and
>> uploaded it to DELAYED/2. Please feel free to tell me if I
>> should delay it longer.
>
> I noted that the last uploads done by Sebastian were NMUs, so hope it
> is uncontroversial that I rescheduled the fix to delayed/0 and direct
> upload tonight. There is not particular reason for the urgency, it's
> more that I would like to base the bullseye-security just on top of
> the 5.2.5-2.1 versioned 5.2.5-2.1~deb11u1 and have additionally the
> fix first exposed in unstable enough as well for regression testing.

No problem at all.  Thanks for your work!  (And I'd be happy to have
a new maintainer or co-maintainer if you're interested. :))

Thanks,
Jonathan

Bug#1009426: xkcdpass: FTBFS: test case raises “TypeError: … missing 1 required positional argument: 'self'”

[Ben Finney]

Control: tags -1 + confirmed upstream
Control: forwarded -1 
https://github.com/redacted/XKCD-password-generator/issues/138
Control: retitle -1 xkcdpass: FTBFS: test case raises “TypeError: … missing 1 
required positional argument: 'self'”
Control: summary -1 0

The upstream test suite has a buggy test case that is raising
TypeError in recent Python versions.

On 12-Apr-2022, Lucas Nussbaum wrote:

> Relevant part (hopefully):
> > […]
> >dh_auto_test -O--buildsystem=pybuild
> > I: pybuild base:239: python3.10 setup.py test 
> > running test
> > […]
> > 
> > ==
> > ERROR: test_entropy_printout_valid_input 
> > (tests.test_xkcdpass.TestEntropyInformation)
> > --
> > TypeError: TestEntropyInformation.test_entropy_printout_valid_input() 
> > missing 1 required positional argument: 'self'
> > 
> > --
> > Ran 9 tests in 0.189s
> > 
> > FAILED (errors=1)
> > […]

I have described this error in the test case in the upstream issue
https://github.com/redacted/XKCD-password-generator/issues/138>.

-- 
 \ “For every complex problem, there is a solution that is simple, |
  `\   neat, and wrong.” —Henry L. Mencken |
_o__)  |
Ben Finney 


signature.asc
Description: PGP signature

Bug#1006457: Chromium fails to start on aarch64 systems

[Andres Salomon]

On Sat, 2 Apr 2022 00:06:04 +0200 MichaIng wrote:
>
> Package: chromium
> Version: 99.0.4844.74-1~deb11u1
>
> > Which boards did you test with?
>
> We observed the issue on these boards:
> - Odroid C2
> - Odroid C4
> - Odroid N2+
> - Radxa ROCK Pi 4
> - Radxa Zero
>
> > What desktops were you using? Was this under X or wayland? Does it
> make a difference if you run chromium with --ozone-platform=x11 or
> --ozone-platform=wayland ? What about --use-gl=desktop ?
>

Thanks. Do you have libglapi-mesa installed, and if so, what version? If 
not, does installing it help?


Same question for libgl1-mesa-dri.

Bug#997970: ITP: linkify-it-py -- links recognition library with full unicode support

[Emmanuel Arias]

Hi,

Thanks to tackle this.

Cheers,

--
Emmanuel Arias
@eamanu
yaerobi.com



OpenPGP_0xFA9DEC5DE11C63F1.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1009618: Firmware "beige-goby*", for Radeon RX6500XT, missing from package

[David Steele]

Package: firmware-amd-graphics

Version: 20210818-1

Severity: Normal

thanks


The RX6500XT was released in January. It requires the "beige-goby" line 
of firmware files, which were added upstream September of last year [1].


A refresh of the package is needed.


[1]: 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=62fd279be67cd6e46aa33a342579f6356ea60634

Bug#1009617: mailscripts: new script to reinject a message via sendmail: sendmail-reinject

[Jameson Graef Rollins]

Package: mailscripts
Version: 0.24-1
Severity: wishlist
Tags: patch

Attached is a patch (via git format-patch) for a script to re-inject
an existing message via sendmail.  The script extracts the sender and
all recipients from the message and constructs the appropriate
sendmail command to re-send the message.  This is very useful for
messages that were fcc'd but for some reason failed to make it out on
an initial pass (e.g. MTA misconfiguration).  A man page is also
included.

Thanks for the useful package!

jamie.


-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (600, 'testing'), (500, 'unstable-debug'), (200, 'unstable'), 
(101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.16.0-5-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages mailscripts depends on:
ii  libconfig-tiny-perl2.28-1
ii  libfile-which-perl 1.23-1
ii  libipc-system-simple-perl  1.30-1
ii  liblist-moreutils-perl 0.430-2
ii  libmail-box-perl   3.009-1
ii  perl   5.34.0-3
ii  python33.9.8-1

Versions of packages mailscripts recommends:
ii  devscripts   2.22.1
ii  git  1:2.35.1-1
ii  libgit-wrapper-perl  0.048-1
ii  notmuch  0.35-2
ii  python3-argcomplete  1.12.3-0.1
ii  python3-gssapi   1.6.12-2
ii  python3-pgpy 0.5.4-4

Versions of packages mailscripts suggests:
ii  gnutls-bin 3.7.3-4+b1
ii  gpg2.2.27-3+b1
ii  gpg-agent  2.2.27-3+b1
ii  gpgsm  2.2.27-3+b1
pn  libdbd-sqlite3-perl
ii  libemail-date-format-perl  1.005-1.1
ii  libio-socket-ssl-perl  2.074-2
ii  libmailtools-perl  2.21-1
ii  libmime-lite-perl  3.033-1
ii  libtry-tiny-perl   0.31-1
pn  libxml-feed-perl   
ii  openssl1.1.1n-1

-- no debconf information
>From 69693dcd497a2fae7f6eb7bdeb0545120b2cb0a6 Mon Sep 17 00:00:00 2001
From: Jameson Graef Rollins 
Date: Tue, 12 Apr 2022 13:03:53 -0700
Subject: [PATCH] new script to reinject message via sendmail

---
 sendmail-reinject   | 70 +
 sendmail-reinject.1.pod | 41 
 2 files changed, 111 insertions(+)
 create mode 100755 sendmail-reinject
 create mode 100644 sendmail-reinject.1.pod

diff --git a/sendmail-reinject b/sendmail-reinject
new file mode 100755
index 000..dfc18d5
--- /dev/null
+++ b/sendmail-reinject
@@ -0,0 +1,70 @@
+#!/usr/bin/env python3
+
+import sys
+import argparse
+import subprocess
+
+import email
+from email.policy import default
+from email.utils import parseaddr, getaddresses
+
+
+def sendmail(recipients, message, sender):
+"""send message via sendmail"""
+cmd = [
+'sendmail',
+'-f', sender,
+] + recipients
+print(' '.join(cmd), file=sys.stderr)
+subprocess.run(
+cmd,
+input=message.as_bytes(),
+check=True,
+)
+
+
+def main():
+parser = argparse.ArgumentParser(
+description="Reinject an email message via sendmail.",
+)
+pgroup = parser.add_mutually_exclusive_group(required=True)
+pgroup.add_argument(
+'message', nargs='?', type=argparse.FileType('rb'),
+help="email message path or '-' for stdin",
+)
+pgroup.add_argument(
+'-i', '--id',
+help="message ID for notmuch extraction",
+)
+
+args = parser.parse_args()
+
+if args.id:
+import notmuch2 as notmuch
+db = notmuch.Database()
+query = f'id:{args.id}'
+assert db.count_messages(query) == 1, "Message ID does not match 
exactly one message??"
+for msg in db.messages(query):
+path = msg.path
+break
+f = open(path, 'rb')
+else:
+f = args.message
+
+# parse the email message
+msg = email.message_from_binary_file(f, policy=default)
+
+sender = parseaddr(msg['from'])[1]
+
+# extract all recipients
+tos = msg.get_all('to', [])
+ccs = msg.get_all('cc', [])
+resent_tos = msg.get_all('resent-to', [])
+resent_ccs = msg.get_all('resent-cc', [])
+recipients = [r[1] for r in getaddresses(tos + ccs + resent_tos + 
resent_ccs)]
+
+sendmail(recipients, msg, sender)
+
+
+if __name__ == '__main__':
+main()
diff --git a/sendmail-reinject.1.pod b/sendmail-reinject.1.pod
new file mode 100644
index 000..ed2ac22
--- /dev/null
+++ b/sendmail-reinject.1.pod
@@ -0,0 +1,41 @@
+=encoding utf8
+
+=head1 NAME
+
+sendmail-reinject - reinject an e-mail via sendmail
+
+=head1 SYNOPSIS
+
+B B
+
+B B<-> 
+
+B B<--id> B
+
+=head1 DESCRIPTION
+
+B reinjects a message to your MTA via sen

Bug#1008849: shiboken2 - Needs tighter dependency on python3

[Nicholas D Steeves]

Hi Yuri,

Yuri D'Elia  writes:
[snip]
>   Built with: '3.9' Detected: '3.10'
>
> due to python3 now defaulting to python3.10.
>

Thank you for reporting this bug :-)

[snip]
>
> This also requires that shiboken2 should be currently rebuilt.
>

Agreed.

> Either the python3 dependency should be tightened, or FORCE_LIMITED_API
> should be used.

These are not the only available options.  Are you aware of binNMUs?
  https://wiki.debian.org/binNMU

Regards,
Nicholas


signature.asc
Description: PGP signature

Bug#1002053: lintian: false positive inconsistent-appstream-metadata-license (gpl-2.0+ != gpl-2+)

[Nicholas D Steeves]

Gentle ping :-)

Regards,
Nicholas


signature.asc
Description: PGP signature

Bug#1005912: hydrogen: autopkgtest regression on arm64 and ppc64el: H2Core::Instrument::dequeue(): Assertion `__queued > 0' failed.

[Nicholas D Steeves]

Hi Paul,

Thank you once again for taking the time to reply :-)

Paul Gevers  writes:
> On 02-04-2022 00:13, Nicholas D Steeves wrote:
>>> On 24-02-2022 06:13, Nicholas D Steeves wrote:
[snip]
>> It's been a few months since I contacted the CI Team about
>> isolation-machines, but they're not yet ready for use either.
>
> That's still correct, and I don't expect that to change in the short 
> term. We're more focused on adding other architectures to enable the 
> Release Team to test all release architectures and maintaining the 
> infrastructure as-is. That's already more work that I'd expected upfront.
>

That makes sense and is totally understandable.  Someday some KVM and/or
possibly QEMU (foreign arch emulated) isolation machines would be really
nice.

[snip]
>> I completely understand, and the only way this request would be
>> justifiable is if it provided a meaningful boost in quality assurance
>> for audio-related packages.
>
> I'm wondering if this warrants a new autopkgtest restrictions (probably 
> not): isolation-machine-or-needs-${group-of-defined-kernel-modules}. I 
> have the feeling that could become a big list for all kind of use cases.
>

Agreed, and yeah, that maintaining that list doesn't seem like a good
use of time.

>> When I contacted upstream, I learned that the cause may be that the CLI
>> utilities are poorly maintained.  Is this sufficient justification for
>> disabling the autopkgtests ie: that it's due diligence and not laziness?
>
> Well, if a test is truly flaky for whatever reason, ci.d.n and the 
> Release Team agree that the test should either not be run or marked as 
> flaky. The latter only has value if some human still regularly checks. 
> The same goes for failure on a particular architecture. If you believe 
> the failure is due to CI and not because the package itself is wrong, 
> then just don't test there (Architecture field in d/t/control). If the 
> package is broken and can't reasonably be fixed, have it removed from 
> that architecture (in unstable; ftp.debian.org pseudo package) and don't 
> build on that architecture anymore. In that case CI found out that the 
> package is broken and that's a good thing.
>

Oh!  I hadn't considered the option of dropping an architecture.  Thank
you, I'll consider this option in the future :-)

>> Thank you again for having this conversation.  I want to support our CI
>> team and technical excellence rather than just "unblock migration to
>> testing", but will of course defer to your recommendations.
>
> Sometimes you need to (for the time being) take a practical stance. I'm 
> not saying yet that we'll not enable the snd-dummy module (I hope for 
> follow-up), but in the present case, if the test can't reliably run on 
> the present infrastructure, and nobody is promising a solution on the 
> short term, you should not make your own live too hard and you should 
> not run the tests for now. Or prepare for the isolation-machine 
> situation (I think Ubuntu has that on most architectures) and hope it 
> will arrive someday in Debian too.
>

Please add me to CC in the follow-up from the CI Team, wherever that
discussion is occurring :-)

It took a while, but upstream was able to identify arm64-specific bugs
(it's fortuitous that the new Apple computers use this arch); I verified that
the fix worked with an upload of a snapshot of their development branch
to our experimental suite, then asked for a backport to the 1.1.x
branch.  Given that the release team appears to have prioritised removal
of this package, I am going to upload a development snapshot of this
1.1.x branch momentarily, even though it doesn't include any
documentation.  At least it resolves this bug!

Regards,
Nicholas


signature.asc
Description: PGP signature

Bug#1009097: meson: (autopkgtest) needs update for python3.10: MesonVersionMismatchException.__init__() missing 1 required positional argument: 'current_version'

[Stefano Rivera]

Hi Jussi (2022.04.09_07:18:01_-0400)
> This is due to we having to poke distutils internals because Debian
> patched distutils to produce different results for install directories
> than sysconfig (the latter was incorrect). Is there now a guarantee
> that starting with 3.10 sysconfig points to the correct place (I don't
> remember the details, but it had something to do with dist-packages vs
> site-packages).

distutils is scheduled for removal in 3.12, so more tools are relying on
sysconfig being correct, which lead us to fixing that.

See: https://lists.debian.org/debian-python/2022/03/msg00039.html

sysconfig is now correct, and you can rely on it staying that way.
However, that doesn't mean everything is straight-forward. You'll need
to figure out what the right way to approach these changes in meson is.

I was pointed to bug 1009452 today that is probably fallout from this
change. Not knowing meson at all, I don't know what the correct approach
to tackle it in Meson is. But I'll do my best to advice you.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Bug#995940: Reproduced on Fujitsu Lifebook U9311

[Stephan Balmer]

Saw the same error on a Fujitsu Lifebook U9311 booting from the current
Debian 11.3 ISO.

Bug#1009247: RFS: importlab/0.7-1 [ITP] -- Library to calculate Python dependency graphs

[Lev Borodin]

Control: tags -1 - moreinfo

> 12 апр. 2022 г., в 22:37, Jeroen Ploemen  wrote:
> 
> Please remove the moreinfo tag (and CC me directly) once you have an
> updated package ready.

Hi Jeron,

thank you for review, that was very helpful!

You can see diff:
 
https://salsa.debian.org/faunris/importlab/-/compare/00367a3651968b2c437119d584ed3c0a3a8424c9...9400c104bc13c35b7893402a9b1551c6332aafb8?from_project_id=69256
 


Pipelines:
https://salsa.debian.org/faunris/importlab/-/pipelines 


New package deployed to:
https://mentors.debian.net/package/importlab/ 




signature.asc
Description: Message signed with OpenPGP

Bug#1009417: saga: FTBFS: configure: error: cannot import Python module "distutils".

[Sebastiaan Couwenberg]

On 4/12/22 20:23, Lucas Nussbaum wrote:

checking for python script directory (pythondir)... 
${PYTHON_PREFIX}/lib/python3.10/site-packages
checking for python extension module directory (pyexecdir)... 
${PYTHON_EXEC_PREFIX}/lib/python3.10/site-packages
checking for python3.10... (cached) /usr/bin/python3
checking for a version of Python >= '2.1.0'... yes
checking for the distutils Python package... no
configure: error: cannot import Python module "distutils".
Please check your Python installation. The error was:
:1: DeprecationWarning: The distutils package is deprecated and slated 
for removal in Python 3.12. Use setuptools or check PEP 632 for potential alternatives


Johan can you fix this (upstream)?

And has the mRMR license issue been addressed upstream to unblock 
updating the package to 8.x?


Kind Regards,

Bas

--
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Bug#1009615: forcibly starts chromium on several functions

[Toni Mueller]

Package: nextcloud-desktop
Version: 3.1.1-2+deb11u1
Severity: important
Tags: upstream


Hi,

I am running nextcloud-desktop in my .xsessionrc. When it starts, it
also fires up chromium, which I have installed, but which I rarely use.
Also, for a number of other activities, which were formerly part of the
nextcloud desktop client, it now also fires up chromium, although
chromium is not my standard browser. I have not found a way to make
nextcloud-client use my standard browser, which happens to be
firefox-esr, for such things, and I am also not prepared to run a second
browser in parallel just to interact with Nextcloud. In fact, I interact
with Nextcloud just fine using Firefox, and if these functions are only
available in the browser these days, they should imho be removed from
the menu. I can start a web browser myself, thank you very much!


Thanks,
Toni



-- System Information:
Debian Release: 11.3
  APT prefers stable-security
  APT policy: (990, 'stable-security'), (990, 'stable'), (500, 
'stable-updates'), (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-13-amd64 (SMP w/12 CPU threads)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages nextcloud-desktop depends on:
ii  libc6  2.31-13+deb11u3
ii  libcloudproviders0 0.3.0-3
ii  libgcc-s1  10.2.1-6
ii  libglib2.0-0   2.66.8-1
ii  libnextcloudsync0  3.1.1-2+deb11u1
ii  libqt5core5a   5.15.2+dfsg-9
ii  libqt5dbus55.15.2+dfsg-9
ii  libqt5gui5 5.15.2+dfsg-9
ii  libqt5keychain10.10.0-1
ii  libqt5network5 5.15.2+dfsg-9
ii  libqt5qml5 5.15.2+dfsg-6
ii  libqt5quick5   5.15.2+dfsg-6
ii  libqt5quickcontrols2-5 5.15.2+dfsg-2
ii  libqt5sql5-sqlite  5.15.2+dfsg-9
ii  libqt5svg5 5.15.2-3
ii  libqt5webenginecore5   5.15.2+dfsg-3
ii  libqt5webenginewidgets55.15.2+dfsg-3
ii  libqt5webkit5  5.212.0~alpha4-11
ii  libqt5widgets5 5.15.2+dfsg-9
ii  libstdc++6 10.2.1-6
ii  nextcloud-desktop-common   3.1.1-2+deb11u1
ii  nextcloud-desktop-l10n 3.1.1-2+deb11u1
ii  qml-module-qtgraphicaleffects  5.15.2-2
ii  qml-module-qtqml-models2   5.15.2+dfsg-6
ii  qml-module-qtquick-controls2   5.15.2+dfsg-2
ii  qml-module-qtquick-layouts 5.15.2+dfsg-6
ii  qml-module-qtquick-window2 5.15.2+dfsg-6
ii  qml-module-qtquick25.15.2+dfsg-6

Versions of packages nextcloud-desktop recommends:
ii  nextcloud-desktop-doc  3.1.1-2+deb11u1

nextcloud-desktop suggests no packages.

-- no debconf information

Bug#1009383: gromacs: FTBFS: AttributeError: module 'collections' has no attribute 'Iterable'

[Nicholas Breen]

tags 1009383 + pending
thanks


Fix pending in git, which is (preferably) waiting on upload until votca
finally clears NEW


-- 
Nicholas Breen
nbr...@debian.org

Bug#1009374: podman: fails to install: unable to open '/usr/lib/systemd/user/podman.socket.dpkg-new': No such file or directory

[Antonio Terceiro]

On Tue, Apr 12, 2022 at 02:33:50PM -0300, Antonio Terceiro wrote:
> Package: podman
> Version: 4.0.1+ds1-3
> Severity: serious
> Justification: fails to install
> 
> I wanted to try podman 4.0 from experimental, but I can't install it:
> This is on a testing machine, with unstable and experimental available,
> but with testing at a higher priority:
> 
> 8<8<8<-
> $ sudo LANG=C apt install -t experimental -qy podman
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Suggested packages:
>   containers-storage
> The following packages will be upgraded:
>   podman
> 1 upgraded, 0 newly installed, 0 to remove and 306 not upgraded.
> Need to get 0 B/10.5 MB of archives.
> After this operation, 3781 kB of additional disk space will be used.
> (Reading database ... 774204 files and directories currently installed.)
> Preparing to unpack .../podman_4.0.1+ds1-3_amd64.deb ...
> Unpacking podman (4.0.1+ds1-3) over (3.4.4+ds1-1) ...
> dpkg: error processing archive 
> /var/cache/apt/archives/podman_4.0.1+ds1-3_amd64.deb (--unpack):
>  unable to open '/usr/lib/systemd/user/podman.socket.dpkg-new': No such file 
> or directory
> /usr/bin/deb-systemd-helper: error: unable to read podman.socket
> Errors were encountered while processing:
>  /var/cache/apt/archives/podman_4.0.1+ds1-3_amd64.deb
> needrestart is being skipped since dpkg has failed
> E: Sub-process /usr/bin/dpkg returned an error code (1)
> 8<8<8<-

This is because podman is shipping both /lib/systemd/user/podman.socket
and /usr/lib/systemd/user/podman.socket:

$ dpkg --contents podman_4.0.1+ds1-3_amd64.deb  | grep socket
-rw-r--r-- root/root   176 2022-02-23 23:41 
./lib/systemd/system/podman.socket
-rw-r--r-- root/root   176 2022-03-06 19:16 ./lib/systemd/user/podman.socket
-rw-r--r-- root/root   176 2022-02-23 23:41 
./usr/lib/systemd/user/podman.socket

You can either ship one of the other, because if /lib is a symlink to
/usr/lib, one will overwrite the other. Indeed, If I revert the test VM
to unmerged-usr filesystem, then podman installs just fine.

I'm pushing a change (commit 699e6f68cd) that fixes this, I hope the
maintainers don't mind.


signature.asc
Description: PGP signature

Bug#1009359: New security upgrade prevent Chromium from starting

[Andres Salomon]

On 4/12/22 08:02, Anthony Callegaro wrote:

Hi guys,

I tried a few additional things to try to sort it out :
-   downgraded to my latest upgrade date :
cat /etc/apt/sources.list.d/snapshot.list
deb [check-valid-until=no] 
http://snapshot.debian.org/archive/debian-security/20220404T151623Z/ 
stable-security main contrib non-free
cat /etc/apt/preferences.d/snapshot.pref
Package: *
Pin: origin snapshot.debian.org
Pin-Priority: 1001
apt update
apt upgrade
- Also downgraded the flatpak dependencies (as there was some mesa.GL upgrade)

So I guess that during the first Chromium run it changed a default parameter in 
my profile (enabling some hardware accelaration or so) which broke it. So I 
will try to reset my profile and keep you updated.

Cheers




Speaking of mesa.GL, it occurs to me that libgles2 and other GL 
libraries should really be in your depends/recommends/suggests lists, 
but they're not (probably because they're detected and dlopened at 
runtime, similar to the problem we had in #1005230). What version of the 
following packages do you have installed?


libgles2 libgl1-mesa-dri libllvm11 libdrm-amdgpu1 libdrm-intel1 
libdrm-nouveau2 libdrm-radeon1 libdrm2 libva-drm2 libva-x11-2 
libigdgmm11 libvulkan1 libglapi-mesa libglx-mesa0 libglx0 libgl1 libglvnd0



We don't have swiftshader enabled in debian chromium packages, so if 
there's something wrong with your hardware acceleration stuff, we don't 
have a good fallback.

Bug#1009613: ITP: rime-scj -- Rime Input Method Engine schema data - Fast Cangjie

[Boyuan Yang]

Package: wnpp
Severity: wishlist

* Package name: rime-scj
  Version : 0.0~git20190120
  Upstream Author : Gong Chen 
* URL : https://github.com/rime/rime-scj
* License : GPL-3.0
  Programming Lang: N/A
  Description : Rime Input Method Engine schema data - Fast Cangjie

 RIME is the acronym of Rime Input Method Engine.
 .
 RIME is a lightweight, extensible input method engine supporting various
input
 schemas including glyph-based input methods, romanization-based input methods
 as well as those for Chinese dialects. It has the ability to compose phrases
 and sentences intelligently and provide very accurate traditional Chinese
 output. RIME's cross-platform core library is written in C++, and can work
 consistently on different platforms with OS-specific wrappers.
 .
 This package provides the fast cangjie schema data of RIME.

This package will be part of the effort to migrate from
https://tracker.debian.org/pkg/brise to https://github.com/rime/plum by
splitting individual data packages and maintaining them individually. The new
binary package rime-data-scj6 will replace old librime-data-scj6
provided by src:brise.

I plan to maintain this package under Debian Input Method Team:
https://salsa.debian.org/input-method-team/rime-scj .

Thanks,
Boyuan Yang


signature.asc
Description: This is a digitally signed message part

Bug#1009614: findimagedupes: inline C code is out of date

[Jonathan H N Chin]

Package: findimagedupes
Version: 2.19.1-1+b1
Severity: normal
X-Debbugs-Cc: c...@jhnc.org

Hi debian maintainers, thanks for all your work.
I'm the author of findimagedupes.


The original findimagedupes Perl script includes inline C code
and autogenerates files at runtime in: /usr/local/lib/findimagedupes

The debian package modifies the Perl script to use pre-generated
files that it installs into: /usr/lib/.../perl5/...

However it seems the Debian build process uses an old version of
the inline C code, and does not check if it has changed.

(In this instance it is not problematic; I had only replaced the
"simplecountbits" function with something even simpler. But it might
be a problem in future if the code ever changes in a more major way.)


-jonathan


-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-8-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_USER
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages findimagedupes depends on:
ii  libc6   2.33-7
ii  libfile-mimeinfo-perl   0.32-1
ii  libgraphics-magick-perl 1.4+really1.3.38-1
ii  libinline-c-perl0.82-1
ii  libinline-perl  0.86-1
ii  perl5.34.0-4
ii  perl-base [perlapi-5.34.0]  5.34.0-4

findimagedupes recommends no packages.

findimagedupes suggests no packages.

-- no debconf information

Bug#995753: qimgv: Crashes trying to display video

[Boyuan Yang]

Control: notfound 995753 1.0.2-1
Control: close 995753

On Fri, 08 Oct 2021 15:51:52 +0300 Vladimir K  wrote:
> Confirming, the cause is partial mesa upgrade. 
> Got the full mesa set from unstable today, no longer having this issue.

Given that the core issue is partial mesa upgrade which has been solved long
ago, I am closing this issue. If you find similar bugs, please open a new bug
report.

Thanks,
Boyuan Yang


signature.asc
Description: This is a digitally signed message part

Bug#1009612: ruby-i18n breaks ruby-i18n-inflector autopkgtest: cannot load such file -- i18n/core_ext/hash

[Paul Gevers]

Source: ruby-i18n, ruby-i18n-inflector
Control: found -1 ruby-i18n/1.10.0-1
Control: found -1 ruby-i18n-inflector/2.6.7-1
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

With a recent upload of ruby-i18n the autopkgtest of ruby-i18n-inflector 
fails in testing when that autopkgtest is run with the binary packages 
of ruby-i18n from unstable. It passes when run with only packages from 
testing. In tabular form:


   passfail
ruby-i18n  from testing1.10.0-1
ruby-i18n-inflectorfrom testing2.6.7-1
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of ruby-i18n to 
testing [1]. Due to the nature of this issue, I filed this bug report 
against both packages. Can you please investigate the situation and 
reassign the bug to the right package?


More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=ruby-i18n

https://ci.debian.net/data/autopkgtest/testing/amd64/r/ruby-i18n-inflector/20787594/log.gz


┌──┐
│ Checking Rubygems dependency resolution on ruby3.0 
   │

└──┘

GEM_PATH= ruby3.0 -e gem\ \"i18n-inflector\"

┌──┐
│ Run tests for ruby3.0 from debian/ruby-tests.rb 
   │

└──┘

RUBYLIB=. GEM_PATH= ruby3.0 debian/ruby-tests.rb
mv lib ./.gem2deb.lib
mv Gemfile.lock ./.gem2deb.Gemfile.lock
/tmp/autopkgtest-lxc.q998h7he/downtmp/build.U3q/src/test/inflector_test.rb:468: 
warning: key :s is duplicated and overwritten on line 468
/tmp/autopkgtest-lxc.q998h7he/downtmp/build.U3q/src/test/inflector_test.rb:479: 
warning: key :s is duplicated and overwritten on line 479
/tmp/autopkgtest-lxc.q998h7he/downtmp/build.U3q/src/test/inflector_test.rb:488: 
warning: key :s is duplicated and overwritten on line 488

test_declarative is deprecated for Test::Unit::TestCase
:85:in 
`require': cannot load such file -- i18n/core_ext/hash (LoadError)
	from 
:85:in 
`require'
	from /usr/lib/ruby/vendor_ruby/i18n-inflector/interpolate.rb:10:in 
`'
	from 
:85:in 
`require'
	from 
:85:in 
`require'

from /usr/lib/ruby/vendor_ruby/i18n-inflector.rb:15:in `'
	from 
:85:in 
`require'
	from 
:85:in 
`require'
	from 
/tmp/autopkgtest-lxc.q998h7he/downtmp/build.U3q/src/test/test_helper.rb:3:in 
`'
	from 
:85:in 
`require'
	from 
:85:in 
`require'
	from 
/tmp/autopkgtest-lxc.q998h7he/downtmp/build.U3q/src/test/inflector_test.rb:1:in 
`'
	from 
:85:in 
`require'
	from 
:85:in 
`require'

from debian/ruby-tests.rb:7:in `block in '
from debian/ruby-tests.rb:7:in `each'
from debian/ruby-tests.rb:7:in `'
mv ./.gem2deb.lib lib
mv ./.gem2deb.Gemfile.lock Gemfile.lock
autopkgtest [23:11:09]: test gem2deb-test-runner



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1009438: mapnik: FTBFS: ImportError: cannot import name 'Iterable' from 'collections' (/usr/lib/python3.10/collections/__init__.py)

[Sebastiaan Couwenberg]

Control: tags -1 pending

On 4/12/22 20:17, Lucas Nussbaum wrote:

ImportError: cannot import name 'Iterable' from 'collections' 
(/usr/lib/python3.10/collections/__init__.py)


This was fixed in git some time ago.

Kind Regards,

Bas

--
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Bug#1009278: kodi: cannot switch language in regional settings

[Vasyl Gello]

Hi Alban!

>For already installed kodi-repository-kodi your fix requires the user to go to
>Settings > Add-ons > Install from repository 
>and there right click on "Kodi Add-on repository" and clicking on
>"Check for update".
>That fixed the language addon version and the installation went fine.
>
>For new kodi-repository-kodi installs, no "Check for updates" is required.

I wonder how you ended up with kodi-repository-kodi not installed.
It is listed in the "Recommends" section of kodi package.

>PS: I do not know how people with only kodi-repository-kodi as
>Kodi repository defined can trigger the "Check for updates"
>if they have an obsolete cache of the manifest.
>But I leave that for another reporter if the issue arise or even exists.
>Ie my box where kodi-repository-kodi was not installed, when
>installing it, I get "Install from repository" in Add-ons but not "Kodi
>Add-on repository" (I believe because that is the sole repository that
>is defined on this kodi instance). Thus nothing to right click upon to
>get "Check for updates".

If people want to disable add-on repository completely, they either
do not install recommended packages including k-r-k or just remove
the package. This is an intended behavior for Debian's vision of user
freedoms. What you found is an unintended side effect of such
configuration.

I guess we should bundle essential add-ons like language packs into
kodi-data package, so that a completely offline system retains the
core functiinality.


-- 
Vasyl Gello
==
Certified SolidWorks Expert

Mob.:+380 (98) 465 66 77

E-Mail: vasek.ge...@gmail.com
==
호랑이는 죽어서 가죽을 남기고 사람은 죽어서 이름을 남긴다

Bug#1009427: zchunk: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=8 meson test returned exit code 4

[Peter Pentchev]

On Tue, Apr 12, 2022 at 09:18:34PM +0200, Bastian Germann wrote:
> Am 12.04.22 um 21:04 schrieb Peter Pentchev:
> > Thanks for filing this. I fixed it yesterday in the salsa Git repo for
> > zchunk packaging:
> > 
> >  
> > https://salsa.debian.org/pkg-rpm-team/zchunk/-/commit/79c480ffa9df4305c3fc5b0bfc4a553625e4c811
> > 
> > I intend to upload this in the next day or so; I was mainly waiting for
> > the libzstd update to 1.5.x to hit the archive.
> 
> The change is included in 1.2.*, so importing them would be preferrable.

Almost. Yeah, sorry, in the hurry to reply I forgot to mention that
I have a (not yet uploaded to salsa) update to 1.2.1 (and that's where
I got most of that patch) and that that update is what I actually intend
to upload in the next day or so, but zchunk 1.2.1 does not include
the special case for a test that produces different checksums for
1.5.0 and 1.4.10 (most likely because 1.4.10 came out really recently).
and there has been no real incentive for the zchunk developers to
support it, since almost everyone has moved on to 1.5.x).

So yeah, my update to zchunk-1.2.1 will still carry a version of that
patch that only includes the 1.4.10 special case (and yes, I will submit
it upstream, just in case).

G'luck,
Peter

-- 
Peter Pentchev  r...@ringlet.net r...@debian.org p...@storpool.com
PGP key:http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint 2EE7 A7A5 17FC 124C F115  C354 651E EFB0 2527 DF13


signature.asc
Description: PGP signature

Bug#1009610: node-querystring: FTBFS: ERROR: Coverage for statements (89.09%) does not meet global threshold (100%)

[Lucas Nussbaum]

Source: node-querystring
Version: 0.2.1-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/querystring
>   /bin/sh -ex debian/tests/pkg-js/test
> + tap test
> TAP version 13
> ok 1 - test/common-index.js # SKIP no tests found {
> Running all tests:
>   test basic
> ✓ prase id=918854443121279438895193
>   test that the canonical qs is parsed properly
> ✓ parse foo=918854443121279438895193
> ✓ parse foo=bar
> ✓ parse foo=bar&foo=quux
> ✓ parse foo=1&bar=2
> ✓ parse my+weird+field=q1%212%22%27w%245%267%2Fz8%29%3F
> ✓ parse foo%3Dbaz=bar
> ✓ parse foo=baz=bar
> ✓ parse str=foo&arr=1&arr=2&arr=3&somenull=&undef=
> ✓ parse  foo = bar 
> ✓ parse foo=%EF%BF%BD
> ✓ parse 
> hasOwnProperty=x&toString=foo&valueOf=bar&__defineGetter__=baz
> ✓ parse foo&bar=baz
>   test that the colon test cases can do the same
> ✓ parse foo:bar -> ; :
> ✓ parse foo:bar;foo:quux -> ; :
> ✓ parse foo:1&bar:2;baz:quux -> ; :
> ✓ parse foo%3Abaz:bar -> ; :
> ✓ parse foo:baz:bar -> ; :
>   test the weird objects, that they get parsed properly
> ✓ parse regexp=
> ✓ parse regexp=
> ✓ parse fn=
> ✓ parse fn=
> ✓ parse math=
> ✓ parse e=
> ✓ parse d=
> ✓ parse d=
> ✓ parse f=&t=
> ✓ parse f=false&t=true
> ✓ parse n=
> ✓ parse nan=
> ✓ parse inf=
>   test non munge test cases
> ✓ stringify {} -> & =
> ✓ stringify {"foo":["bar","baz"]} -> & =
> ✓ stringify {"blah":"burp"} -> & =
> ✓ stringify {"gragh":["1","3"],"goo":"2"} -> & =
> ✓ stringify 
> {"frappucino":"muffin","goat[]":"scone","pond":"moose"} -> & =
> ✓ stringify {"trololol":"yes","lololo":"no"} -> & =
>   test the nested qs-in-qs case
> ✓ parse a=b&q=x%3Dy%26y%3Dz
>   test nested in colon
> ✓ stringify {"a":"b","qs.stringify -> q":{"x":"y","y":"z"}} -> ; 
> : 
> ✓ parse undefined
>   test stringifying
> ✓ stringify {"foo":"918854443121279438895193"}
> ✓ stringify {"foo":"bar"}
> ✓ stringify {"foo":["bar","quux"]}
> ✓ stringify {"foo":"1","bar":"2"}
> ✓ stringify {"my weird field":"q1!2\"'w$5&7/z8)?"}
> ✓ stringify {"foo=baz":"bar"}
> ✓ stringify {"foo":"baz=bar"}
> ✓ stringify 
> {"str":"foo","arr":["1","2","3"],"somenull":"","undef":""}
> ✓ stringify {" foo ":" bar "}
> ✓ stringify {"foo":"�"}
> ✓ stringify 
> {"hasOwnProperty":"x","toString":"foo","valueOf":"bar","__defineGetter__":"baz"}
> ✓ stringify {"foo":"","bar":"baz"}
> ✓ stringify {"foo":[]}
> ✓ stringify {"foo":[],"bar":"baz"}
&

Bug#1009607: node-readable-stream: FTBFS: ERROR: Coverage for statements (94.31%) does not meet global threshold (100%)

[Lucas Nussbaum]

Source: node-readable-stream
Version: 3.6.0+~cs3.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
> Link node_modules/bufferstreams -> ../bufferstreams
>dh_auto_build --buildsystem=nodejs
> No build command found, searching known files
> No build command found, searching known files
>dh_auto_test --buildsystem=nodejs
>   ln -s ../debian/tests/test_modules/buf-compare node_modules/buf-compare
>   ln -s ../debian/tests/test_modules/call-bind node_modules/call-bind
>   ln -s ../debian/tests/test_modules/core-assert node_modules/core-assert
>   ln -s ../debian/tests/test_modules/deep-strict-equal 
> node_modules/deep-strict-equal
>   ln -s ../debian/tests/test_modules/events.once node_modules/events.once
>   ln -s ../debian/tests/test_modules/get-intrinsic 
> node_modules/get-intrinsic
>   ln -s ../debian/tests/test_modules/is-error node_modules/is-error
>   ln -s ../debian/tests/test_modules/object.getownpropertydescriptors 
> node_modules/object.getownpropertydescriptors
>   ln -s ../debian/tests/test_modules/util-promisify 
> node_modules/util-promisify
>   ln -s ../. node_modules/readable-stream
>   /bin/sh -ex debian/tests/pkg-js/test
> + export NODE_PATH=debian/tests/test_modules
> + tap -J test/parallel/test-readable-from.js 
> test/parallel/test-readable-large-hwm.js 
> test/parallel/test-readable-single-end.js 
> test/parallel/test-stream-auto-destroy.js 
> test/parallel/test-stream-backpressure.js 
> test/parallel/test-stream-big-packet.js test/parallel/test-stream-big-push.js 
> test/parallel/test-stream-buffer-list.js 
> test/parallel/test-stream-decoder-objectmode.js 
> test/parallel/test-stream-destroy-event-order.js 
> test/parallel/test-stream-duplex-destroy.js 
> test/parallel/test-stream-duplex-end.js test/parallel/test-stream-duplex.js 
> test/parallel/test-stream-end-paused.js 
> test/parallel/test-stream-events-prepend.js 
> test/parallel/test-stream-finished.js test/parallel/test-stream-ispaused.js 
> test/parallel/test-stream-objectmode-undefined.js 
> test/parallel/test-stream-once-readable-pipe.js 
> test/parallel/test-stream-pipe-after-end.js 
> test/parallel/test-stream-pipe-await-drain-manual-resume.js 
> test/parallel/test-stream-pipe-await-drain-push-while-write.js 
> test/parallel/test-stream-pipe-await-drain.js 
> test/parallel/test-stream-pipe-cleanup-pause.js 
> test/parallel/test-stream-pipe-cleanup.js 
> test/parallel/test-stream-pipe-error-handling.js 
> test/parallel/test-stream-pipe-event.js 
> test/parallel/test-stream-pipe-flow-after-unpipe.js 
> test/parallel/test-stream-pipe-flow.js 
> test/parallel/test-stream-pipe-manual-resume.js 
> test/parallel/test-stream-pipe-multiple-pipes.js 
> test/parallel/test-stream-pipe-same-destination-twice.js 
> test/parallel/test-stream-pipe-unpipe-streams.js 
> test/parallel/test-stream-pipe-without-listenerCount.js 
> test/parallel/test-stream-pipeline-queued-end-in-destroy.js 
> test/parallel/test-stream-pipeline.js test/parallel/test-stream-push-order.js 
> test/parallel/test-stream-push-strings.js 
> test/parallel/test-stream-readable-async-iterators.js 
> test/parallel/test-stream-readable-constructor-set-methods.js 
> test/parallel/test-stream-readable-destroy.js 
> test/parallel/test-stream-readable-emittedReadable.js 
> test/parallel/test-stream-readable-event.js 
> test/parallel/test-stream-readable-flow-recursion.js 
> test/parallel/test-stream-readable-hwm-0-async.js 
> test/parallel/test-stream-readable-hwm-0-no-flow-data.js 
> test/parallel/test-stream-readable-hwm-0.js 
> test/parallel/test-stream-readable-infinite-read.js 
> test/parallel/test-stream-readable-invalid-chunk.js 
> test/parallel/test-stream-readable-needReadable.js 
> test/parallel/test-stream-readable-no-unneeded-readable.js 
> test/parallel/test-stream-readable-object-multi-push-async.js 
> test/parallel/test-stream-readable-pause-and-resume.js 
> test/parallel/test-stream-readable-readable-then-resume.js 
> test/parallel/test-stream-readable-reading-readingMore.js 
> test/parallel/test-stream-readable-resume-hwm.js 
> test/parallel/test-stream-readable-resumeScheduled.js 
> test/parallel/test-stream-readable-setEncoding-existing-buffers.js 
> test/parallel/test-stream-readable-setEncoding-null.js 
> test/parallel/test-stream-readable-with-unimplemented-_read.js 
> test/parallel/test-stream-readableListening-state.js 
> test/p

Bug#1009606: node-browserify-aes: FTBFS: ERROR: Coverage for statements (97.19%) does not meet global threshold (100%)

[Lucas Nussbaum]

Source: node-browserify-aes
Version: 1.2.0-4
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/browserify-aes
>   /bin/sh -ex debian/tests/pkg-js/test
> + tap -R spec test/index.js
> 
> (node:3873976) [DEP0106] DeprecationWarning: crypto.createCipher is 
> deprecated.
> (Use `node --trace-deprecation ...` to show where the warning was created)
> (node:3873976) [DEP0005] DeprecationWarning: Buffer() is deprecated due to 
> security and usability issues. Please use the Buffer.alloc(), 
> Buffer.allocUnsafe(), or Buffer.from() methods instead.
> (node:3873976) Warning: Use Cipheriv for counter mode of aes-128-ctr
> (node:3873976) Warning: Use Cipheriv for counter mode of aes-192-ctr
> (node:3873976) Warning: Use Cipheriv for counter mode of aes-256-ctr
> (node:3873976) Warning: Use Cipheriv for counter mode of aes-128-ctr
> (node:3873976) Warning: Use Cipheriv for counter mode of aes-192-ctr
> (node:3873976) Warning: Use Cipheriv for counter mode of aes-256-ctr
> (node:3873976) Warning: Use Cipheriv for counter mode of aes-128-ctr
> (node:3873976) Warning: Use Cipheriv for counter mode of aes-192-ctr
> (node:3873976) Warning: Use Cipheriv for counter mode of aes-256-ctr
> (node:3873976) Warning: Use Cipheriv for counter mode of aes-128-ctr
> (node:3873976) Warning: Use Cipheriv for counter mode of aes-192-ctr
> (node:3873976) Warning: Use Cipheriv for counter mode of aes-256-ctr
> (node:3873976) Warning: Use Cipheriv for counter mode of aes-128-ctr
> (node:3873976) Warning: Use Cipheriv for counter mode of aes-192-ctr
> (node:3873976) Warning: Use Cipheriv for counter mode of aes-256-ctr
> (node:3873976) Warning: Use Cipheriv for counter mode of aes-128-ctr
> (node:3873976) Warning: Use Cipheriv for counter mode of aes-192-ctr
> (node:3873976) Warning: Use Cipheriv for counter mode of aes-256-ctr
> (node:3873976) Warning: Use Cipheriv for counter mode of aes-128-ctr
> (node:3873976) Warning: Use Cipheriv for counter mode of aes-192-ctr
> (node:3873976) Warning: Use Cipheriv for counter mode of aes-256-ctr
> test/index.js
> 
>   ✓ should be strictly equal
> 
>   ✓ intermediate
> 
>   ✓ intermediate 2
> 
>   ✓ final
> 
>   ✓ should be strictly equal
> 
>   ✓ intermediate
> 
>   ✓ intermediate 2
> 
>   ✓ should be strictly equal
> 
>   ✓ final
> 
>   ✓ should be strictly equal
> 
>   ✓ intermediate
> 
>   ✓ intermediate 2
> 
>   ✓ final
> 
>   ✓ should be strictly equal
> 
>   ✓ intermediate
> 
>   ✓ intermediate 2
> 
>   ✓ should be strictly equal
> 
>   ✓ final
> 
>   ✓ should be strictly equal
> 
>   ✓ intermediate
> 
>   ✓ intermediate 2
> 
>   ✓ final
> 
>   ✓ should be strictly equal
> 
>   ✓ intermediate
> 
>   ✓ intermediate 2
> 
>   ✓ should be strictly equal
> 
>   ✓ final
> 
>   ✓ should be strictly equal
> 
>   ✓ intermediate
> 
>   ✓ intermediate 2
> 
>   ✓ final
> 
>   ✓ should be strictly equal
> 
>   ✓ intermediate
> 
>   ✓ intermediate 2
> 
>   ✓ should be strictly equal
> 
>   ✓ final
> 
>   ✓ should be strictly equal
> 
>   ✓ intermediate
> 
>   ✓ intermediate 2
> 
>   ✓ final
> 
>   ✓ should be strictly equal
> 
>   ✓ intermediate
> 
>   ✓ intermediate 2
> 
>   ✓ should be strictly equal
> 
>   ✓ final
> 
>   ✓ should be strictly equal
> 
>   ✓ intermediate
> 
>   ✓ intermediate 2
> 
>   ✓ final
> 
>   ✓ should be strictly equal
> 
>   ✓ intermediate
> 
>   ✓ intermediate 2
> 
>   ✓ should be strictly equal
> 
>   ✓ final
> 
>   ✓ should be strictly equal
> 
>   ✓ intermediate
> 
>   ✓ intermediate 2
> 
>   ✓ final
> 
>   ✓ should be strictly equal
> 
>   ✓ intermediate
> 
>   ✓ intermediate 2
> 
>   ✓ should be strictly equal
> 
>   ✓ final
> 
>   ✓ should be strictly equal
> 
>   ✓ intermediate
> 
>   ✓ intermediate 2
> 
>   ✓ final
> 
>   ✓ should be strictly equal
> 
>   ✓ intermediate
> 
>   ✓ intermediate 2
> 
>   ✓ should be strictly equal
> 
>   ✓ final
> 
>   ✓ should be strictly equal
> 
>   ✓ intermediate

Bug#1009605: node-browser-pack: FTBFS: ERROR: Coverage for statements (94.36%) does not meet global threshold (100%)

[Lucas Nussbaum]

Source: node-browser-pack
Version: 6.1.0+ds+~6.1.1-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):
> make[1]: Entering directory '/<>'
> uglifyjs -m < prelude.js  | sed -e 's/;[[:space:]]*$//g' -e 
> '/^[[:space:]]*$/d' | tr -d '\n' > _prelude.mangle.js
> uglifyjs -c unused=false,expression=true,passes=5  < _prelude.mangle.js | sed 
> -e 's/;[[:space:]]*$//g' -e '/^[[:space:]]*$/d' | tr -d '\n' > _prelude.js
> dh override_dh_auto_build
> make[1]: Leaving directory '/<>'
>dh_auto_test --buildsystem=nodejs
>   ln -s ../. node_modules/browser-pack
>   /bin/sh -ex debian/tests/pkg-js/test
> + tap -R spec test/comment.js test/empty.js test/not_found.js 
> test/only_execute_entries.js test/order.js test/pack.js test/raw.js 
> test/source-maps-existing.js test/source-maps.js test/this.js test/unicode.js
> 
> (node:217151) DeprecationWarning: deepEqual() is deprecated, use same() 
> instead
> (Use `node --trace-deprecation ...` to show where the warning was created)
> test/comment.js
>   trailing comment
> 
> ✓ expect truthy value
> 
> ✓ should be equal
> 
> ✓ should be equal
> 
> ✓ should be equal
> 
> ✓ expected to throw
> 
> test/empty.js
>   empty
> 
> ✓ expected to not throw
> 
>   empty with standalone
> 
> ✓ expected to not throw
> 
> (node:217185) [DEP0005] DeprecationWarning: Buffer() is deprecated due to 
> security and usability issues. Please use the Buffer.alloc(), 
> Buffer.allocUnsafe(), or Buffer.from() methods instead.
> (Use `node --trace-deprecation ...` to show where the warning was created)
> (node:217185) DeprecationWarning: deepEqual() is deprecated, use same() 
> instead
> test/not_found.js
>   not found
> 
> ✓ expect truthy value
> 
> ✓ should be equal
> 
> ✓ should be equal
> 
> ✓ should be equal
> 
> ✓ expected to throw
> 
> ✓ should be equal
> 
> test/only_execute_entries.js
>   raw
> 
> ✓ expect truthy value
> 
> test/order.js
>   raw
> 
> ✓ should be equivalent
> 
> test/pack.js
>   pack
> 
> ✓ expect truthy value
> 
> ✓ should be equal
> 
> ✓ should be equal
> 
> ✓ should be equal
> 
> test/raw.js
>   raw
> 
> ✓ expect truthy value
> 
> ✓ should be equal
> 
> ✓ should be equal
> 
> ✓ should be equal
> 
> ✓ expected to throw
> 
> test/source-maps-existing.js
>   pack one file with source file field and existing sourcemap
> 
> ✓ first original mappings are same
> 
> ✓ last original mappings are same
> 
> ✓ first generated columns are same
> 
> ✓ last generated columns are same
> 
> ✓ first generated line is offset by 1
> 
> ✓ last generated line is offset by 1
> 
> ✓ removes orinal source maps
> 
> test/source-maps.js
>   pack one file with source file field and one without
> 
> ✓ expect truthy value
> 
> ✓ should be equal
> 
> ✓ should be equal
> 
> ✓ should be equal
> 
> ✓ contains source mapping url as last line
> 
> ✓ includes mappings for sourceFile and prelude only
> 
> ✓ adds offset mapping for each line
> 
>   pack two files with source file field
> 
> ✓ expect truthy value
> 
> ✓ should be equal
> 
> ✓ should be equal
> 
> ✓ should be equal
> 
> ✓ contains source mapping url as last line
> 
> ✓ includes mappings for both files and prelude
> 
> ✓ adds offset mapping for each line
> 
>   pack two files without source file field
> 
> ✓ expect truthy value
> 
> ✓ should be equal
> 
> ✓ should be equal
> 
> ✓ should be equal
> 
> ✓ contains no source mapping url
> 
>   pack two files with source file field, one with nomap flag
> 
> ✓ expect truthy value
> 
> ✓ should be equal
> 
> ✓ should be equal
> 
> ✓ should be equal
> 
> ✓ contains source mapping url as last line
> 
> ✓ includes mappings for only the file without the "nomap" flag and prelude
> 
> ✓ adds offset mapping for each line of mapped file
> 
>   custom sourceMapPrefix for //@
> 
> ✓ expect truthy value
> 
> ✓ should be equal
> 
> ✓ should be equal
> 
> ✓ should be equal
> 
> ✓ contains source mapping url as last lin

Bug#1009604: node-ieee754: FTBFS: ERROR: Coverage for statements (77.96%) does not meet global threshold (100%)

[Lucas Nussbaum]

Source: node-ieee754
Version: 1.2.1-2
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/ieee754
>   /bin/sh -ex debian/tests/pkg-js/test
> + tap -R spec test/basic.js
> 
> test/basic.js
> 
>   ✓ should be truthy
> 
>   ✓ should be truthy
> 
>   ✓ should be truthy
> 
>   ✓ should be truthy
> 
>   4 passing (906.328ms)
> ERROR: Coverage for lines (77.96%) does not meet global threshold (100%)
> ERROR: Coverage for branches (48.78%) does not meet global threshold (100%)
> ERROR: Coverage for statements (77.96%) does not meet global threshold (100%)
> --|-|--|-|-|
> File  | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s
>   
> --|-|--|-|-|
> All files |   77.96 |48.78 | 100 |   77.96 |  
>   
>  index.js |   77.96 |48.78 | 100 |   77.96 | 
> 25,27,48-49,53-54,59,62-63,67-68,73-74 
> --|-|--|-|-|
> 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-ieee754_1.2.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=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.

Bug#1009603: node-ripemd160: FTBFS: ERROR: Coverage for branches (91.66%) does not meet global threshold (100%)

[Lucas Nussbaum]

Source: node-ripemd160
Version: 2.0.2-6
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/ripemd160
>   /bin/sh -ex debian/tests/pkg-js/test
> + tap test/index.js
> TAP version 13
> ok 1 - test/index.js # time=1776.483ms {
> # vector #1 with .update
> ok 1 should be deeply equivalent
> # vector #1 with streams
> ok 2 should be deeply equivalent
> # vector #2 with .update
> ok 3 should be deeply equivalent
> # vector #2 with streams
> ok 4 should be deeply equivalent
> # vector #3 with .update
> ok 5 should be deeply equivalent
> # vector #3 with streams
> ok 6 should be deeply equivalent
> # vector #4 with .update
> ok 7 should be deeply equivalent
> # vector #4 with streams
> ok 8 should be deeply equivalent
> # vector #5 with .update
> ok 9 should be deeply equivalent
> # vector #5 with streams
> ok 10 should be deeply equivalent
> # vector #6 with .update
> ok 11 should be deeply equivalent
> # vector #6 with streams
> ok 12 should be deeply equivalent
> # vector #7 with .update
> ok 13 should be deeply equivalent
> # vector #7 with streams
> ok 14 should be deeply equivalent
> # vector #8 with .update
> ok 15 should be deeply equivalent
> # vector #8 with streams
> ok 16 should be deeply equivalent
> # vector #9 with .update
> ok 17 should be deeply equivalent
> # vector #9 with streams
> ok 18 should be deeply equivalent
> # vector #10 with .update
> ok 19 should be deeply equivalent
> # vector #10 with streams
> ok 20 should be deeply equivalent
> # vector #11 with .update
> ok 21 should be deeply equivalent
> # vector #11 with streams
> ok 22 should be deeply equivalent
> # vector #12 with .update
> ok 23 should be deeply equivalent
> # vector #12 with streams
> ok 24 should be deeply equivalent
> # vector #13 with .update
> ok 25 should be deeply equivalent
> # vector #13 with streams
> ok 26 should be deeply equivalent
> # vector #14 with .update
> ok 27 should be deeply equivalent
> # vector #14 with streams
> ok 28 should be deeply equivalent
> # vector #15 with .update
> ok 29 should be deeply equivalent
> # vector #15 with streams
> ok 30 should be deeply equivalent
> # vector #16 with .update
> ok 31 should be deeply equivalent
> # vector #16 with streams
> ok 32 should be deeply equivalent
> # vector #17 with .update
> ok 33 should be deeply equivalent
> # vector #17 with streams
> ok 34 should be deeply equivalent
> # vector #18 with .update
> ok 35 should be deeply equivalent
> # vector #18 with streams
> ok 36 should be deeply equivalent
> # vector #19 with .update
> ok 37 should be deeply equivalent
> # vector #19 with streams
> ok 38 should be deeply equivalent
> # vector #20 with .update
> ok 39 should be deeply equivalent
> # vector #20 with streams
> ok 40 should be deeply equivalent
> # vector #21 with .update
> ok 41 should be deeply equivalent
> # vector #21 with streams
> ok 42 should be deeply equivalent
> # vector #22 with .update
> ok 43 should be deeply equivalent
> # vector #22 with streams
> ok 44 should be deeply equivalent
> # vector #23 with .update
> ok 45 should be deeply equivalent
> # vector #23 with streams
> ok 46 should be deeply equivalent
> # vector #24 with .update
> ok 47 should be deeply equivalent
> # vector #24 with streams
> ok 48 should be deeply equivalent
> # vector #25 with .update
> ok 49 should be deeply equivalent
> # vector #25 with streams
> ok 50 should be deeply equivalent
> # vector #26 with .update
> ok 51 should be deeply equivalent
> # vector #26 with streams
> ok 52 should be deeply equivalent
> # vector #27 with .update
> ok 53 should be deeply equivalent
> # vector #27 with streams
> ok 54 should be deeply equivalent
> # vector #28 wit

Bug#1009602: node-optimist: FTBFS: ERROR: Coverage for statements (77.24%) does not meet global threshold (100%)

[Lucas Nussbaum]

Source: node-optimist
Version: 0.6.1+~0.0.30-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
> Link node_modules/@types/optimist -> ../../types-optimist
>dh_auto_build --buildsystem=nodejs
> No build command found, searching known files
> No build command found, searching known files
>dh_auto_test --buildsystem=nodejs
>   ln -s ../. node_modules/optimist
>   /bin/sh -ex debian/tests/pkg-js/test
> + grep -v test/parse.js
> + grep -v+  test/_.js
> ls test/_.js test/dash.js test/parse.js test/parse_modified.js test/short.js 
> test/usage.js test/whitespace.js
> + tap test/dash.js test/parse_modified.js test/short.js test/usage.js 
> test/whitespace.js
> TAP version 13
> (node:3944650) DeprecationWarning: deepEqual() is deprecated, use same() 
> instead
> (Use `node --trace-deprecation ...` to show where the warning was created)
> ok 1 - test/dash.js # time=34.587ms {
> # Subtest: -
> 1..5
> ok 1 - should be equivalent
> ok 2 - should be equivalent
> ok 3 - should be equivalent
> ok 4 - should be equivalent
> ok 5 - should be equivalent
> ok 1 - - # time=24.757ms
> 
> 1..1
> # time=34.587ms
> }
> 
> (node:3944651) DeprecationWarning: deepEqual() is deprecated, use same() 
> instead
> (Use `node --trace-deprecation ...` to show where the warning was created)
> ok 2 - test/parse_modified.js # time=19.24ms {
> # Subtest: parse with modifier functions
> 1..1
> ok 1 - should be equivalent
> ok 1 - parse with modifier functions # time=12.826ms
> 
> 1..1
> # time=19.24ms
> }
> 
> ok 3 - test/short.js # time=17.082ms {
> # Subtest: -n123
> 1..1
> ok 1 - should be equal
> ok 1 - -n123 # time=7.994ms
> 
> # Subtest: -123
> 1..3
> ok 1 - should be equal
> ok 2 - should be equal
> ok 3 - should be equal
> ok 2 - -123 # time=1.646ms
> 
> 1..2
> # time=17.082ms
> }
> 
> ok 4 - test/usage.js # time=59.216ms {
> # Subtest: usageFail
> ok 1 - should be equivalent
> ok 2 - should be equivalent
> ok 3 - should be equivalent
> ok 4 - expect truthy value
> 1..4
> ok 1 - usageFail # time=12.824ms
> 
> # Subtest: usagePass
> ok 1 - should be equivalent
> 1..1
> ok 2 - usagePass # time=2.626ms
> 
> # Subtest: checkPass
> ok 1 - should be equivalent
> 1..1
> ok 3 - checkPass # time=2.399ms
> 
> # Subtest: checkFail
> ok 1 - should be equivalent
> ok 2 - should be equivalent
> ok 3 - should be equivalent
> ok 4 - expect truthy value
> 1..4
> ok 4 - checkFail # time=3.13ms
> 
> # Subtest: checkCondPass
> ok 1 - should be equivalent
> 1..1
> ok 5 - checkCondPass # time=1.705ms
> 
> # Subtest: checkCondFail
> ok 1 - should be equivalent
> ok 2 - should be equivalent
> ok 3 - should be equivalent
> ok 4 - expect truthy value
> 1..4
> ok 6 - checkCondFail # time=2.882ms
> 
> # Subtest: countPass
> ok 1 - should be equivalent
> 1..1
> ok 7 - countPass # time=1.653ms
> 
> # Subtest: countFail
> ok 1 - should be equivalent
> ok 2 - should be equivalent
> ok 3 - should be equivalent
> ok 4 - expect truthy value
> 1..4
> ok 8 - countFail # time=2.386ms
> 
> # Subtest: defaultSingles
> ok 1 - should be equivalent
> 1..1
> ok 9 - defaultSingles # time=1.623ms
> 
> # Subtest: defaultAliases
> ok 1 - should be equivalent
> 1..1
> ok 10 - defaultAliases # time=1.382ms
> 
> # Subtest: defaultHash
> ok 1 - should be equivalent
> 1..1
> ok 11 - defaultHash # time=1.28ms
> 
> # Subtest: rebase
> ok 1 - should be equal
> ok 2 - should be equal
> ok 3 - should be equal
> 1..3
> ok 12 - rebase # time=1.136ms
> 
> 1..12
> # time=59.216ms
> }
> 
> ok 5 - test/whitespace.js # time=10.551ms {
> # Subtest: whitespace should be whitespace
> 1..1
&g

Bug#1009601: node-serve-static: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1

[Lucas Nussbaum]

Source: node-serve-static
Version: 1.14.2+~1.13.10-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
> Link node_modules/@types/serve-static -> ../../types-serve-static
>dh_auto_build --buildsystem=nodejs
> No build command found, searching known files
> No build command found, searching known files
>dh_auto_test --buildsystem=nodejs
>   ln -s ../. node_modules/serve-static
>   /bin/sh -ex debian/tests/pkg-js/test
> + mocha -C --timeout 1 --bail --check-leaks --require should
> 
> 
>   serveStatic()
> basic operations
>   undefined should require root path
>   undefined should require root path to be string
>   undefined should serve static files
>   undefined should support nesting
>   1) should set Content-Type
> 
> 
>   4 passing (50ms)
>   1 failing
> 
>   1) serveStatic()
>basic operations
>  should set Content-Type:
>  Error: expected "Content-Type" of "text/plain; charset=UTF-8", got 
> "text/plain"
>   at Context. (test/test.js:44:10)
>   at callFnAsync (/usr/share/nodejs/mocha/lib/runnable.js:394:21)
>   at Test.Runnable.run (/usr/share/nodejs/mocha/lib/runnable.js:338:7)
>   at Runner.runTest (/usr/share/nodejs/mocha/lib/runner.js:678:10)
>   at /usr/share/nodejs/mocha/lib/runner.js:801:12
>   at next (/usr/share/nodejs/mocha/lib/runner.js:593:14)
>   at /usr/share/nodejs/mocha/lib/runner.js:603:7
>   at next (/usr/share/nodejs/mocha/lib/runner.js:486:14)
>   at Immediate._onImmediate (/usr/share/nodejs/mocha/lib/runner.js:571:5)
>   at processImmediate (internal/timers.js:464:21)
>   
>   at Test._assertHeader (/usr/share/nodejs/supertest/lib/test.js:236:14)
>   at /usr/share/nodejs/supertest/lib/test.js:306:17
>   at Test._assertFunction (/usr/share/nodejs/supertest/lib/test.js:285:13)
>   at Test.assert (/usr/share/nodejs/supertest/lib/test.js:164:23)
>   at Server.localAssert (/usr/share/nodejs/supertest/lib/test.js:120:14)
>   at emitCloseNT (net.js:1671:8)
>   at processTicksAndRejections (internal/process/task_queues.js:81:21)
> 
> 
> 
> 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-serve-static_1.14.2+~1.13.10-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.

Bug#1009600: node-safe-buffer: FTBFS: dh_auto_test: error: cd ./safer-buffer && sh -ex ../debian/nodejs/safer-buffer/test returned exit code 1

[Lucas Nussbaum]

Source: node-safe-buffer
Version: 5.2.1+~cs2.1.2-2
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
> Link node_modules/safer-buffer -> ../safer-buffer
>dh_auto_build --buildsystem=nodejs
> No build command found, searching known files
> No build command found, searching known files
>dh_auto_test --buildsystem=nodejs
>   ln -s ../. node_modules/safe-buffer
>   cd ./safer-buffer && sh -ex ../debian/nodejs/safer-buffer/test
> + tape tests.js
> TAP version 13
> # Default is Safer
> ok 1 should be strictly equal
> ok 2 should not be strictly equal
> ok 3 should not be strictly equal
> # Is not a function
> ok 4 should be strictly equal
> ok 5 should be strictly equal
> ok 6 should be strictly equal
> ok 7 should be strictly equal
> ok 8 should be strictly equal
> ok 9 should be strictly equal
> ok 10 should be strictly equal
> ok 11 should be strictly equal
> # Constructor throws
> ok 12 should throw
> ok 13 should throw
> ok 14 should throw
> ok 15 should throw
> ok 16 should throw
> ok 17 should throw
> ok 18 should throw
> ok 19 should throw
> ok 20 should throw
> ok 21 should throw
> ok 22 should throw
> ok 23 should throw
> ok 24 should throw
> ok 25 should throw
> ok 26 should throw
> ok 27 should throw
> ok 28 should throw
> ok 29 should throw
> ok 30 should throw
> ok 31 should throw
> ok 32 should throw
> ok 33 should throw
> ok 34 should throw
> ok 35 should throw
> # Safe methods exist
> ok 36 alloc
> ok 37 from
> ok 38 alloc
> ok 39 from
> ok 40 alloc
> ok 41 from
> # Unsafe methods exist only in Dangerous
> ok 42 should be strictly equal
> ok 43 should be strictly equal
> ok 44 should be strictly equal
> ok 45 should be strictly equal
> ok 46 should be strictly equal
> ok 47 should be strictly equal
> # Generic methods/properties are defined and equal
> ok 48 poolSize
> ok 49 poolSize
> ok 50 poolSize
> ok 51 poolSize
> ok 52 poolSize
> ok 53 poolSize
> ok 54 isBuffer
> ok 55 isBuffer
> ok 56 isBuffer
> ok 57 isBuffer
> ok 58 isBuffer
> ok 59 isBuffer
> ok 60 concat
> ok 61 concat
> ok 62 concat
> ok 63 concat
> ok 64 concat
> ok 65 concat
> ok 66 byteLength
> ok 67 byteLength
> ok 68 byteLength
> ok 69 byteLength
> ok 70 byteLength
> ok 71 byteLength
> # Built-in buffer static methods/properties are inherited
> ok 72 Blob
> ok 73 Blob
> ok 74 Blob
> ok 75 Blob
> ok 76 Blob
> ok 77 Blob
> ok 78 transcode
> ok 79 transcode
> ok 80 transcode
> ok 81 transcode
> ok 82 transcode
> ok 83 transcode
> ok 84 kMaxLength
> ok 85 kMaxLength
> ok 86 kMaxLength
> ok 87 kMaxLength
> ok 88 kMaxLength
> ok 89 kMaxLength
> ok 90 kStringMaxLength
> ok 91 kStringMaxLength
> ok 92 kStringMaxLength
> ok 93 kStringMaxLength
> ok 94 kStringMaxLength
> ok 95 kStringMaxLength
> ok 96 btoa
> ok 97 btoa
> ok 98 btoa
> ok 99 btoa
> ok 100 btoa
> ok 101 btoa
> ok 102 atob
> ok 103 atob
> ok 104 atob
> ok 105 atob
> ok 106 atob
> ok 107 atob
> ok 108 constants
> ok 109 constants
> ok 110 constants
> ok 111 constants
> ok 112 constants
> ok 113 constants
> ok 114 INSPECT_MAX_BYTES
> ok 115 INSPECT_MAX_BYTES
> ok 116 INSPECT_MAX_BYTES
> ok 117 INSPECT_MAX_BYTES
> ok 118 INSPECT_MAX_BYTES
> ok 119 INSPECT_MAX_BYTES
> # Built-in Buffer static methods/properties are inherited
> ok 120 poolSize
> ok 121 poolSize
> ok 122 poolSize
> ok 123 poolSize
> ok 124 poolSize
> ok 125 poolSize
> ok 126 from
> ok 127 from
> ok 128 from
> ok 129 from
> ok 130 from
> ok 131 from
> ok 132 of
> ok 133 of
> ok 134 of
> ok 135 of
> ok 136 of
> ok 137 of
> ok 138 alloc
> ok 139 alloc
> ok 140 alloc
> ok 141 alloc
> ok 142 alloc
> ok 143 alloc
> ok 144 isBuffer
> ok 145 isBuffer
> ok 146 isBuffer
> ok 147 isBuffer
> ok 148 isBuffer
> ok 149 isBuffer
> ok 150 compare
> ok 151 compare
> ok 152 compare
> ok 153 compare
> ok 154 compare
> ok 155 compare
> ok 156 isEncoding
> ok 157 isEncoding
> ok 158 isEncoding
> ok 159 isEncoding
> ok 160 isEncoding
> ok 161 isEncoding
> ok 162 concat
> ok 163 concat
> ok 164 concat
> ok 165 concat
> ok 166 concat
> ok 167 concat
> ok 168 byteLength
> ok 169 byteLength
> ok 170 byteLength
> ok

Bug#1009599: node-meow: FTBFS: ReferenceError: t is not defined

[Lucas Nussbaum]

Source: node-meow
Version: 8.0.0+~cs3.21.0-3
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
> Link node_modules/decamelize-keys -> ../decamelize-keys
> Link node_modules/hard-rejection -> ../hard-rejection
> Link node_modules/type-fest -> ../type-fest
>dh_auto_build --buildsystem=nodejs
> No build command found, searching known files
> No build command found, searching known files
> No build command found, searching known files
> No build command found, searching known files
>dh_auto_test --buildsystem=nodejs
>   ln -s ../debian/tests/test_modules/human-signals 
> node_modules/human-signals
>   ln -s ../debian/tests/test_modules/onetime node_modules/onetime
>   ln -s ../debian/tests/test_modules/strip-final-newline 
> node_modules/strip-final-newline
>   ln -s ../. node_modules/meow
>   /bin/sh -ex debian/tests/pkg-js/test
> + tape test/is-required-flag.js test/test.js
> /<>/test/test.js:573
>   t.end();
>   ^
> 
> ReferenceError: t is not defined
> at Object. (/<>/test/test.js:573:2)
> at Module._compile (internal/modules/cjs/loader.js:1085:14)
> at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10)
> at Module.load (internal/modules/cjs/loader.js:950:32)
> at Function.Module._load (internal/modules/cjs/loader.js:790:12)
> at Module.require (internal/modules/cjs/loader.js:974:19)
> at require (internal/modules/cjs/helpers.js:101:18)
> at importOrRequire (/usr/share/nodejs/tape/bin/import-or-require.js:14:5)
> at /usr/share/nodejs/tape/bin/tape:90:14
> at Array.reduce ()
> 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-meow_8.0.0+~cs3.21.0-3_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.

Bug#1009598: node-katex: FTBFS: TypeError: this.getOptions is not a function

[Lucas Nussbaum]

Source: node-katex
Version: 0.13.11+~cs6.0.0-3
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
> Link node_modules/babel-plugin-preval -> ../babel-plugin-preval
> Link node_modules/babel-plugin-version-inline -> 
> ../babel-plugin-version-inline
>dh_auto_build --buildsystem=nodejs
> Found debian/nodejs/babel-plugin-version-inline/build
>   cd ./babel-plugin-version-inline && sh -ex 
> ../debian/nodejs/babel-plugin-version-inline/build
> + babeljs src -d lib
> Successfully compiled 1 file with Babel (491ms).
> Found debian/nodejs/babel-plugin-preval/build
>   cd ./babel-plugin-preval && sh -ex 
> ../debian/nodejs/babel-plugin-preval/build
> + babeljs src -d dist
> Successfully compiled 12 files with Babel (810ms).
> Found debian/nodejs/./build
>   cd ./. && sh -ex debian/nodejs/./build
> + rollup -c
> 
> ./katex.js → dist/katex.mjs...
> (!) Circular dependency
> src/functions.js -> src/functions/operatorname.js -> src/macros.js -> 
> src/functions.js
> created dist/katex.mjs in 5.2s
> 
> ./contrib/auto-render/auto-render.js → 
> dist/contrib/auto-render.mjs...
> created dist/contrib/auto-render.mjs in 122ms
> 
> ./contrib/mhchem/mhchem.js → dist/contrib/mhchem.mjs...
> created dist/contrib/mhchem.mjs in 331ms
> 
> ./contrib/copy-tex/copy-tex.js → 
> dist/contrib/copy-tex.mjs...
> created dist/contrib/copy-tex.mjs in 24ms
> 
> ./contrib/mathtex-script-type/mathtex-script-type.js → 
> dist/contrib/mathtex-script-type.mjs...
> created dist/contrib/mathtex-script-type.mjs in 
> 11ms
> 
> ./contrib/render-a11y-string/render-a11y-string.js → 
> dist/contrib/render-a11y-string.mjs...
> created dist/contrib/render-a11y-string.mjs in 
> 85ms
> + webpack
> Hash: 
> c84e0db7fc0ba302d4c1fd263725fdf5c20c4f93e270037a91f4085ec34950c50abd3da7758b6ef1606da249567e95ba5dfb913282f6921719c483b9
> Version: webpack 4.43.0
> Child
> Hash: c84e0db7fc0ba302d4c1
> Time: 9085ms
> Built at: 04/12/2022 4:54:41 PM
>  1 asset
> Entrypoint katex = katex.js
> [0] ./src/katex.less 514 bytes {0} [built] [failed] [1 error]
> [1] ./katex.webpack.js + 82 modules 604 KiB {0} [built]
> | ./katex.webpack.js 396 bytes [built]
> | ./katex.js 5.61 KiB [built]
> | ./src/ParseError.js 1.95 KiB [built]
> | ./src/Settings.js 5.51 KiB [built]
> | ./src/domTree.js 14.2 KiB [built]
> | ./src/fontMetrics.js 7.77 KiB [built]
> | ./src/symbols.js 43.4 KiB [built]
> | ./src/buildCommon.js 20.8 KiB [built]
> | ./src/buildTree.js 1.72 KiB [built]
> | ./src/macros.js 37.8 KiB [built]
> | ./src/parseTree.js 1.29 KiB [built]
> | ./src/Token.js 1.41 KiB [built]
> | ./src/utils.js 2.79 KiB [built]
> | ./src/Style.js 2.92 KiB [built]
> | ./src/unicodeScripts.js 3.37 KiB [built]
> | + 68 hidden modules
> 
> ERROR in ./src/katex.less
> Module build failed (from 
> /usr/share/nodejs/mini-css-extract-plugin/dist/loader.js):
> ModuleBuildError: Module build failed (from 
> /usr/share/nodejs/postcss-loader/dist/cjs.js):
> TypeError: this.getOptions is not a function
> at Object.loader 
> (/usr/share/nodejs/postcss-loader/dist/index.js:40:24)
> at /usr/share/nodejs/webpack/lib/NormalModule.js:316:20
> at /usr/share/nodejs/loader-runner/lib/LoaderRunner.js:399:11
> at /usr/share/nodejs/loader-runner/lib/LoaderRunner.js:251:18
>  @ ./katex.webpack.js 9:0-26
> Child mini-css-extract-plugin 
> ../../../usr/share/nodejs/css-loader/dist/cjs.js??ref--6-1!../../../usr/share/nodejs/postcss-loader/dist/cjs.js??ref--6-2!../../../usr/share/nodejs/less-loader/dist/cjs.js??ref--6-3!src/katex.less:
> Entrypoint mini-css-extract-plugin = *
> [0] 
> /usr/share/nodejs/css-loader/dist/cjs.js??ref--6-1!/usr/share/nodejs/postcss-loader/dist/cjs.js??ref--6-2!/usr/share/nodejs/less-loader/dist/cjs.js??ref--6-3!./src/katex.less
>  215 bytes {0} [built] [f

Bug#1009595: node-buffer-shims: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1

[Lucas Nussbaum]

Source: node-buffer-shims
Version: 1.0.0-4
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/buffer-shims
>   /bin/sh -ex debian/tests/pkg-js/test
> + tape test/alloc.js test/save-unsafe.js
> b.length == 1024
> c.length == 512
> copied 512 bytes from b into c
> copied 512 bytes from c into b w/o sourceEnd
> copied 512 bytes from c into b w/o sourceStart
> copied 512 bytes from b into c w/o targetStart
> copied 256 bytes from end of b into beginning of c
> copied 512 bytes from b trying to overrun c
> copied 768 bytes from b into b
> bytes written to buffer: 11
> uber: 'über'
> f.length: 4 (should be 4)
> f.length: 8 (should be 8)
> f.length: 12 (should be 12)
> bytes written to buffer: 4 (should be 4)
> f.length: 8 (should be 8)
> f.length: 12 (should be 12)
> bytes written to buffer: 4 (should be 4)
> f.length: 8 (should be 8)
> f.length: 12 (should be 12)
> bytes written to buffer: 4 (should be 4)
> f.length: 8 (should be 8)
> f.length: 12 (should be 12)
> bytes written to buffer: 4 (should be 4)
> Create hex string from buffer
> Create buffer from hex string
> Try to slice off the end of the buffer
> 
> 
> 5
> 
> 9
> 
> 4
> 
> 9
> 
> 3
> 
> 2
> 
> 
> 
> 
> 
> 
> 
> 
> assert.js:118
>   throw new AssertionError(obj);
>   ^
> 
> AssertionError [ERR_ASSERTION]: Missing expected exception.
> at Object. (/<>/test/alloc.js:896:8)
> at Module._compile (internal/modules/cjs/loader.js:1085:14)
> at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10)
> at Module.load (internal/modules/cjs/loader.js:950:32)
> at Function.Module._load (internal/modules/cjs/loader.js:790:12)
> at Module.require (internal/modules/cjs/loader.js:974:19)
> at require (internal/modules/cjs/helpers.js:101:18)
> at importOrRequire (/usr/share/nodejs/tape/bin/import-or-require.js:14:5)
> at /usr/share/nodejs/tape/bin/tape:90:14
> at Array.reduce () {
>   generatedMessage: false,
>   code: 'ERR_ASSERTION',
>   actual: undefined,
>   expected: undefined,
>   operator: 'throws'
> }
> 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-buffer-shims_1.0.0-4_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.

Bug#1009597: node-recast: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1

[Lucas Nussbaum]

Source: node-recast
Version: 0.21.0-2
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):
> make[1]: Entering directory '/<>'
> tsc
> make[1]: Leaving directory '/<>'
>dh_auto_test --buildsystem=nodejs
>   ln -s ../. node_modules/recast
>   /bin/sh -ex debian/tests/pkg-js/test
> + mocha -r ts-node/register test/babel.ts
> 
> 
>   Babel
> undefined basic printing (65ms)
> undefined babel 6: should not wrap IIFE when reusing nodes
> undefined should not disappear when surrounding code changes
> undefined should not disappear when an import is added and `export` is 
> used inline
> undefined should not disappear when an import is added and `export 
> default` is used inline
> undefined should not print delimiters with type annotations
> undefined should parenthesize ** operator arguments when lower precedence
> undefined should parenthesize ** operator arguments as needed when same 
> precedence
> undefined should be able to replace top-level statements with leading 
> empty lines
> undefined should parse and print dynamic import(...)
> undefined tolerates circular references (95ms)
> undefined prints numbers in bases other than 10 without converting them
> undefined prints the export-default-from syntax
> undefined avoids extra semicolons on mutated blocks containing a 'use 
> strict' directive
> undefined should print typescript class elements modifiers
> 
> 
>   15 passing (230ms)
> 
> + mocha -r ts-node/register test/comments.ts
> 
> 
>   comments
> undefined [acorn] attachment and reprinting
> undefined [acorn] TrailingComments
> undefined [acorn] BodyTrailingComments
> undefined [acorn] ParamTrailingComments
> undefined [acorn] StatementTrailingComments
> undefined [acorn] ProtoAssignComment
> undefined [acorn] should correctly attach to concise methods
> undefined [acorn] should attach comments as configurable
> undefined [acorn] should be reprinted when modified
> undefined [acorn] should preserve stray non-comment syntax
> undefined [acorn] should be reprinted even if dangling
> undefined [acorn] should attach to program.body[0] instead of program
> undefined [acorn] should not collapse multi line function definitions
> undefined [acorn] should be pretty-printable in illegal positions
> undefined [acorn] should preserve correctness when a return expression 
> has a comment
> undefined [acorn] should wrap in parens when the return expression has 
> nested leftmost comment
> undefined [acorn] should not wrap in parens when the return expression 
> has an interior comment
> undefined [acorn] should correctly handle a lonesome comment (alt 1)
> undefined [acorn] should correctly handle a not-so-lonesome comment (alt 
> 2 - trailing whitespace)
> undefined [acorn] should correctly handle a lonesome comment (alt 3 - 
> trailing whitespace)
> undefined [acorn] should not reformat a return statement that is not 
> modified
> undefined [acorn] should correctly handle a removing the argument from a 
> return
> undefined [acorn] should preserve comments attached to EmptyStatement
> undefined [babel] attachment and reprinting
> undefined [babel] TrailingComments
> undefined [babel] BodyTrailingComments
> undefined [babel] ParamTrailingComments
> undefined [babel] StatementTrailingComments
> undefined [babel] ProtoAssignComment
> undefined [babel] should correctly attach to concise methods
> undefined [babel] should attach comments as configurable
> undefined [babel] should be reprinted when modified
> undefined [babel] should preserve stray non-comment syntax
> undefined [babel] should be reprinted even if dangling
> undefined [babel] should attach to program.body[0] instead of program
> undefined [babel] should not collapse multi line function definitions
> undefined [babel] should be pretty-printable in illegal positions
> undefined [babel] should preserve correctness when a return expression 
> has a comment
> undefined [babel] should wrap in parens when the return expression has 
> nested leftmost comment
> undefined [babel] should not wrap in parens when the return expression 
> has an interior comment
> undefined [babel] should correctly handle a lonesome comment (alt 1)
> undefined [babel] should correctly handle a not-so-lonesome comment (alt 
> 2 - trailing whitespace)

Bug#1009596: node-ts-jest: FTBFS: @babel/helper-get-function-arity is required by debian/nodejs/./extlinks but not available

[Lucas Nussbaum]

Source: node-ts-jest
Version: 27.1.4+~cs0.2.6-2
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
> Link ./node_modules/ansi-regex -> /usr/share/nodejs/ansi-regex
> Link ./node_modules/ansi-styles -> /usr/share/nodejs/ansi-styles
> Link ./node_modules/@babel/code-frame -> /usr/share/nodejs/@babel/code-frame
> Link ./node_modules/@babel/core -> /usr/share/nodejs/@babel/core
> Link ./node_modules/@babel/generator -> /usr/share/nodejs/@babel/generator
> Link ./node_modules/@babel/helper-function-name -> 
> /usr/share/nodejs/@babel/helper-function-name
> Not found
> ### @babel/helper-get-function-arity is required by debian/nodejs/./extlinks 
> but not available
> make: *** [debian/rules:10: binary] Error 1


The full build log is available from:
http://qa-logs.debian.net/2022/04/12/node-ts-jest_27.1.4+~cs0.2.6-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=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.

Bug#1009594: node-syntax-error: FTBFS: ERROR: Coverage for statements (89.65%) does not meet global threshold (100%)

[Lucas Nussbaum]

Source: node-syntax-error
Version: 1.4.0+~1.4.1-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
> Link node_modules/@types/syntax-error -> ../../types-syntax-error
>dh_auto_build --buildsystem=nodejs
> No build command found, searching known files
> No build command found, searching known files
>dh_auto_test --buildsystem=nodejs
>   ln -s ../. node_modules/syntax-error
>   /bin/sh -ex debian/tests/pkg-js/test
> + tap test/check.js test/esm.js test/html.js test/ok.js test/run.js 
> test/run2.js test/shebang.js test/spread.js test/yield.js
> TAP version 13
> ok 1 - test/check.js # time=27.964ms {
> # Subtest: check
> ok 1 - expect truthy value
> ok 2 - should be equal
> ok 3 - should be equal
> ok 4 - should be equal
> ok 5 - expect truthy value
> 1..5
> ok 1 - check # time=20.853ms
> 
> 1..1
> # time=27.964ms
> }
> 
> ok 2 - test/esm.js # time=30.338ms {
> # Subtest: esm with sourceType script
> ok 1 - expect truthy value
> ok 2 - should be equal
> ok 3 - should be equal
> ok 4 - should be equal
> ok 5 - expect truthy value
> 1..5
> ok 1 - esm with sourceType script # time=12.626ms
> 
> # Subtest: esm with sourceType module
> ok 1 - expect falsey value
> 1..1
> ok 2 - esm with sourceType module # time=7.23ms
> 
> 1..2
> # time=30.338ms
> }
> 
> ok 3 - test/html.js # time=13.64ms {
> # Subtest: html
> ok 1 - expect truthy value
> ok 2 - should be equal
> ok 3 - should be equal
> ok 4 - should be equal
> ok 5 - foo.js:1
> 1..5
> ok 1 - html # time=8.926ms
> 
> 1..1
> # time=13.64ms
> }
> 
> ok 4 - test/ok.js # time=16.505ms {
> # Subtest: ok
> ok 1 - expect falsey value
> 1..1
> ok 1 - ok # time=9.305ms
> 
> 1..1
> # time=16.505ms
> }
> 
> ok 5 - test/run.js # time=15.049ms {
> # Subtest: do not run sources
> 1..1
> ok 1 - expect falsey value
> ok 1 - do not run sources # time=7.412ms
> 
> 1..1
> # time=15.049ms
> }
> 
> ok 6 - test/run2.js # time=29.133ms {
> # Subtest: do not run sources (2)
> 1..1
> ok 1 - expect falsey value
> ok 1 - do not run sources (2) # time=10.809ms
> 
> 1..1
> # time=29.133ms
> }
> 
> ok 7 - test/shebang.js # time=21.096ms {
> # Subtest: shebang
> ok 1 - expect falsey value
> 1..1
> ok 1 - shebang # time=14.465ms
> 
> 1..1
> # time=21.096ms
> }
> 
> ok 8 - test/spread.js # time=14.64ms {
> # Subtest: spread
> ok 1 - expect falsey value
> 1..1
> ok 1 - spread # time=7.134ms
> 
> 1..1
> # time=14.64ms
> }
> 
> ok 9 - test/yield.js # time=19.484ms {
> # Subtest: yield
> ok 1 - expect falsey value
> 1..1
> ok 1 - yield # time=4.562ms
> 
> 1..1
> # time=19.484ms
> }
> 
> 1..9
> # time=1519.101ms
> ERROR: Coverage for lines (91.66%) does not meet global threshold (100%)
> ERROR: Coverage for functions (83.33%) does not meet global threshold (100%)
> ERROR: Coverage for branches (80%) does not meet global threshold (100%)
> ERROR: Coverage for statements (89.65%) does not meet global threshold (100%)
> --|-|--|-|-|---
> File  | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s 
> --|-|--|-|-|---
> All files |   89.65 |   80 |   83.33 |   91.66 |   
>  index.js |   89.65 |   80 |   83.33 |   91.66 | 12,56 
> --|-|--|-|-|---
> 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-syntax-error_1.4.0+~1.4.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=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbf

Bug#1009593: node-debbundle-es-to-primitive: FTBFS: dh_auto_test: error: cd ./node-is-callable && sh -ex ../debian/nodejs/node-is-callable/test returned exit code 1

[Lucas Nussbaum]

Source: node-debbundle-es-to-primitive
Version: 1.2.1+~cs9.7.15-2
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
> Link node_modules/has-symbols -> ../node-has-symbols
> Link node_modules/is-callable -> ../node-is-callable
> Link node_modules/is-date-object -> ../node-is-date-object
> Link node_modules/is-symbol -> ../node-is-symbol
> Link node_modules/make-arrow-function -> ../node-make-arrow-function
> Link node_modules/make-generator-function -> ../node-make-generator-function
> Link node_modules/object-is -> ../node-object-is
> Link node_modules/@types/es-to-primitive -> ../../types-es-to-primitive
>dh_auto_build --buildsystem=nodejs
> No build command found, searching known files
> No build command found, searching known files
> No build command found, searching known files
> No build command found, searching known files
> No build command found, searching known files
> No build command found, searching known files
> No build command found, searching known files
> No build command found, searching known files
> No build command found, searching known files
>dh_auto_test --buildsystem=nodejs
>   ln -s ../. node_modules/es-to-primitive
>   cd ./node-is-callable && sh -ex ../debian/nodejs/node-is-callable/test
> + tap -R spec test.js
> 
> test.js
> 
>   1) ENOENT: no such file or directory, stat 'test.js'
> 
>   0 passing (47.142ms)
>   1 failing
> 
>   1) test.js ENOENT: no such file or directory, stat 'test.js':
>  Error: ENOENT: no such file or directory, stat 'test.js'
>   at runAllFiles (/usr/share/nodejs/tap/bin/run.js:652:15)
>   at runTests (/usr/share/nodejs/tap/bin/run.js:783:3)
>   at mainAsync (/usr/share/nodejs/tap/bin/run.js:267:5)
>   at main (/usr/share/nodejs/tap/bin/run.js:141:3)
>   at Object.j.main (/usr/share/nodejs/jackspeak/index.js:483:5)
>   at execute (/usr/share/nodejs/jackspeak/index.js:224:7)
>   at jack (/usr/share/nodejs/jackspeak/index.js:163:31)
>   at module.exports (/usr/share/nodejs/tap/bin/jack.js:28:26)
>   at Object. (/usr/share/nodejs/tap/bin/run.js:874:23)
> 
> --|-|--|-|-|---
> File  | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s 
> --|-|--|-|-|---
> All files |   0 |0 |   0 |   0 |   
> --|-|--|-|-|---
> dh_auto_test: error: cd ./node-is-callable && sh -ex 
> ../debian/nodejs/node-is-callable/test returned exit code 1


The full build log is available from:
http://qa-logs.debian.net/2022/04/12/node-debbundle-es-to-primitive_1.2.1+~cs9.7.15-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=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.

Bug#1009592: node-process-nextick-args: FTBFS: ERROR: Coverage for statements (10%) does not meet global threshold (100%)

[Lucas Nussbaum]

Source: node-process-nextick-args
Version: 2.0.1-2
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/process-nextick-args
>   /bin/sh -ex debian/tests/pkg-js/test
> + tap test.js
> TAP version 13
> (node:1671881) DeprecationWarning: equals() is deprecated, use equal() instead
> (Use `node --trace-deprecation ...` to show where the warning was created)
> ok 1 - test.js # time=22.855ms {
> # Subtest: should work
> 1..5
> ok 1 - expect truthy value
> ok 2 - should be equal
> ok 3 - should be equal
> ok 4 - should be equal
> ok 5 - should be equal
> ok 1 - should work # time=11.104ms
> 
> # Subtest: correct number of arguments
> 1..1
> ok 1 - correct number
> ok 2 - correct number of arguments # time=2.255ms
> 
> # Subtest: uses the current value of process.nextTick
> 1..1
> ok 1 - expect truthy value
> ok 3 - uses the current value of process.nextTick # time=0.699ms
> 
> 1..3
> # time=22.855ms
> }
> 
> 1..1
> # time=731.38ms
> ERROR: Coverage for lines (10%) does not meet global threshold (100%)
> ERROR: Coverage for functions (0%) does not meet global threshold (100%)
> ERROR: Coverage for branches (33.33%) does not meet global threshold (100%)
> ERROR: Coverage for statements (10%) does not meet global threshold (100%)
> --|-|--|-|-|---
> File  | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s 
> --|-|--|-|-|---
> All files |  10 |33.33 |   0 |  10 |   
>  index.js |  10 |33.33 |   0 |  10 | 7,13-41   
> --|-|--|-|-|---
> 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-process-nextick-args_2.0.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=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.

Bug#1009591: node-output-file-sync: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1

[Lucas Nussbaum]

Source: node-output-file-sync
Version: 2.0.1-2
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 ../debian/tests/test_modules/array-to-sentence 
> node_modules/array-to-sentence
>   ln -s ../debian/tests/test_modules/assert-valid-glob-opts 
> node_modules/assert-valid-glob-opts
>   ln -s ../debian/tests/test_modules/get-mode node_modules/get-mode
>   ln -s ../debian/tests/test_modules/glob-option-error 
> node_modules/glob-option-error
>   ln -s ../debian/tests/test_modules/indexed-filter 
> node_modules/indexed-filter
>   ln -s ../debian/tests/test_modules/inspect-with-kind 
> node_modules/inspect-with-kind
>   ln -s ../debian/tests/test_modules/is-utf8 node_modules/is-utf8
>   ln -s ../debian/tests/test_modules/read-utf8-file 
> node_modules/read-utf8-file
>   ln -s ../debian/tests/test_modules/rmfr node_modules/rmfr
>   ln -s ../debian/tests/test_modules/validate-glob-opts 
> node_modules/validate-glob-opts
>   ln -s ../. node_modules/output-file-sync
>   /bin/sh -ex debian/tests/pkg-js/test
> + tape test.js
> TAP version 13
> # outputFileSync()
> ok 1 should return null when it doesn't create any directories.
> ok 2 should return the path of the first created directory.
> ok 3 should throw an error when fs.writeFile fails.
> ok 4 should throw an error when mkdirp fails.
> ok 5 should reflect `mode` option to the directory mode.
> ok 6 should reflect `mode` option to the file mode.
> ok 7 should reflect `dirMode` option to the directory mode.
> ok 8 should reflect `fileMode` option to the file mode.
> ok 9 should create a file into the existing directory.
> ok 10 should create a file into the new directory.
> ok 11 should accept fs.writeFile's option.
> # Argument validation for outputFileSync()
> ok 12 should throw an error when it takes no arguments.
> ok 13 should throw an error when the first argument is not a string.
> ok 14 should throw an error when the first argument is an empty string.
> not ok 15 should throw an error when the second argument is not a valid file 
> content.
>   ---
> operator: throws
> expected: |-
>   '/^TypeError.*Expected file content to be a string, Buffer or 
> Uint8Array, but got Set {} instead\\./'
> actual: |-
>   { [TypeError: Expected file content to be a string, Buffer or 
> Uint8Array, but got Set(0) {} instead.] message: 'Expected file content to be 
> a string, Buffer or Uint8Array, but got Set(0) {} instead.' }
> at: Test. (/<>/test.js:114:4)
> stack: |-
>   TypeError: Expected file content to be a string, Buffer or Uint8Array, 
> but got Set(0) {} instead.
>   at outputFileSync (/<>/index.js:31:9)
>   at /<>/test.js:115:9
>   at Test.throws (/usr/share/nodejs/tape/lib/test.js:632:9)
>   at Test.bound [as throws] (/usr/share/nodejs/tape/lib/test.js:99:32)
>   at Test. (/<>/test.js:114:4)
>   at Test.bound [as _cb] (/usr/share/nodejs/tape/lib/test.js:99:32)
>   at Test.run (/usr/share/nodejs/tape/lib/test.js:117:31)
>   at Test.bound [as run] (/usr/share/nodejs/tape/lib/test.js:99:32)
>   at Immediate.next [as _onImmediate] 
> (/usr/share/nodejs/tape/lib/results.js:88:19)
>   at processImmediate (internal/timers.js:464:21)
>   ...
> ok 16 should throw an error when the third argument is provided but is 
> neither string nor an object.
> not ok 17 should throw an error when the third argument is an invalid 
> encoding.
>   ---
> operator: throws
> expected: |-
>   '/^Error.*for exmaple \'utf8\' and \'ascii\', but got \'utfu\' 
> instead\\./'
> actual: |-
>   { [Error: Expected a string to be a valid encoding, for exmaple 'utf8' 
> and 'ascii', but got 'utf\x00' instead.] message: 'Expected a string to be a 
> valid encoding, for exmaple \'utf8\' and \'ascii\', but got \'utf\\x00\' 
> instead.' }
> at: Test. (/<>/test.js:126:4)
> stack: |-
>   Error: Expected a string to be a valid encoding, for exmaple 'utf8' and 
> 'ascii', 

Bug#1009590: node-npm-bundled: FTBFS: ERROR: Coverage for statements (85.45%) does not meet global threshold (100%)

[Lucas Nussbaum]

Source: node-npm-bundled
Version: 1.1.2-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
> Link node_modules/npm-normalize-package-bin -> ../npm-normalize-package-bin
>dh_auto_build --buildsystem=nodejs
> No build command found, searching known files
> No build command found, searching known files
>dh_auto_test --buildsystem=nodejs
>   ln -s ../. node_modules/npm-bundled
>   /bin/sh -ex debian/tests/pkg-js/test
> + tap test/all-bundle.js test/bad-json.js test/basic.js test/caches.js 
> test/cycle.js test/metadeps.js test/missing-package-json.js test/no-bundle.js 
> test/non-array-bundledeps.js test/pkgtree.js test/readdir-fail.js 
> test/scoped.js test/weird-scope.js -J --100
> TAP version 13
> ok 1 - test/all-bundle.js # time=75.656ms {
> # Subtest: sync
> ok 1 - should be equivalent
> 1..1
> ok 1 - sync # time=21.553ms
> 
> # Subtest: async
> ok 1 - should be equivalent
> 1..1
> ok 2 - async # time=28.082ms
> 
> 1..2
> # time=75.656ms
> }
> 
> ok 2 - test/bad-json.js # time=72.221ms {
> # Subtest: sync
> ok 1 - should be equivalent
> 1..1
> ok 1 - sync # time=16.458ms
> 
> # Subtest: async
> ok 1 - should be equivalent
> 1..1
> ok 2 - async # time=41.327ms
> 
> 1..2
> # time=72.221ms
> }
> 
> ok 3 - test/basic.js # time=52.154ms {
> # Subtest: sync
> ok 1 - should be equivalent
> 1..1
> ok 1 - sync # time=16.167ms
> 
> # Subtest: async
> ok 1 - should be equivalent
> 1..1
> ok 2 - async # time=24.044ms
> 
> 1..2
> # time=52.154ms
> }
> 
> ok 4 - test/caches.js # time=88.34ms {
> # Subtest: sync
> 1..2
> ok 1 - should be equivalent
> ok 2 - should be equivalent
> ok 1 - sync # time=17.609ms
> 
> # Subtest: async
> 1..2
> ok 1 - should be equivalent
> ok 2 - should be equivalent
> ok 2 - async # time=33.933ms
> 
> # Subtest: mixed
> 1..2
> ok 1 - should be equivalent
> ok 2 - should be equivalent
> ok 3 - mixed # time=4.668ms
> 
> # Subtest: mixed, nothing to bundle
> 1..2
> ok 1 - should be equivalent
> ok 2 - should be equivalent
> ok 4 - mixed, nothing to bundle # time=2.444ms
> 
> 1..4
> # time=88.34ms
> }
> 
> ok 5 - test/cycle.js # time=56.363ms {
> # Subtest: sync
> ok 1 - should be equivalent
> 1..1
> ok 1 - sync # time=19.742ms
> 
> # Subtest: async
> ok 1 - should be equivalent
> 1..1
> ok 2 - async # time=18.981ms
> 
> 1..2
> # time=56.363ms
> }
> 
> ok 6 - test/metadeps.js # time=44.13ms {
> # Subtest: sync
> ok 1 - should be equivalent
> 1..1
> ok 1 - sync # time=16.11ms
> 
> # Subtest: async
> ok 1 - should be equivalent
> 1..1
> ok 2 - async # time=15.225ms
> 
> 1..2
> # time=44.13ms
> }
> 
> ok 7 - test/missing-package-json.js # time=58.184ms {
> # Subtest: sync
> ok 1 - should be equivalent
> 1..1
> ok 1 - sync # time=22.076ms
> 
> # Subtest: async
> ok 1 - should be equivalent
> 1..1
> ok 2 - async # time=21.014ms
> 
> 1..2
> # time=58.184ms
> }
> 
> ok 8 - test/no-bundle.js # time=38.046ms {
> # Subtest: sync
> ok 1 - should be equivalent
> 1..1
> ok 1 - sync # time=11.262ms
> 
> # Subtest: async
> ok 1 - should be equivalent
> 1..1
> ok 2 - async # time=13.584ms
> 
> 1..2
> # time=38.046ms
> }
> 
> ok 9 - test/non-array-bundledeps.js # time=48.537ms {
> # Subtest: sync
> ok 1 - should be equivalent
> 1..1
> ok 1 - sync # time=16.678ms
> 
> # Subtest: async
> ok 1 - should be equivalent
> 1..1
> ok 2 - async # time=19.22ms
> 
> 1..2
> # time=48.537ms
> }
> 
> ok 10 - test/pkgtree.js # time=7.114ms {
> ok 1 - this is fine
> 1..1
> # time=7.114ms
> }
> 
> ok 11 - test/readdir

Bug#1009589: node-brfs: FTBFS: ERROR: Coverage for statements (36.84%) does not meet global threshold (100%)

[Lucas Nussbaum]

Source: node-brfs
Version: 2.0.2-2
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/brfs
>   /bin/sh -ex debian/tests/pkg-js/test
> + tap -R spec test/cmd.js
> 
> test/cmd.js
>   cmd.js
> 
> ✓ should be equal
> 
> 
>   1 passing (1s)
> ERROR: Coverage for lines (38.63%) does not meet global threshold (100%)
> ERROR: Coverage for functions (21.05%) does not meet global threshold (100%)
> ERROR: Coverage for branches (42.59%) does not meet global threshold (100%)
> ERROR: Coverage for statements (36.84%) does not meet global threshold (100%)
> -|-|--|-|-|
> File | % Stmts | % Branch | % Funcs | % Lines | Uncovered 
> Line #s  
> -|-|--|-|-|
> All files|   36.84 |42.59 |   21.05 |   38.63 |   
>  
>  node-brfs-2.0.2 |   30.58 |36.36 |   21.05 |   32.05 |   
>  
>   index.js   |   30.58 |36.36 |   21.05 |   32.05 | 
> 12,21,44-74,81-82,85,88,92,109-149 
>  node-brfs-2.0.2/bin |  90 |   70 | 100 |  90 |   
>  
>   cmd.js |  90 |   70 | 100 |  90 | 8 
>  
> -|-|--|-|-|
> 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-brfs_2.0.2-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=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.

Bug#1009587: node-tape: FTBFS: ERROR: Coverage for statements (48.12%) does not meet global threshold (100%)

[Lucas Nussbaum]

Source: node-tape
Version: 5.5.2+~cs8.20.16-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
> Link node_modules/array.prototype.every -> ../array-prototype-every
> Link node_modules/dotignore -> ../dotignore
> Link node_modules/for-each -> ../for-each
> Link node_modules/has-dynamic-import -> ../has-dynamic-import
> Link node_modules/string.prototype.trim -> ../stringprototypetrim
> Link node_modules/@types/tape -> ../../types-tape
>dh_auto_build --buildsystem=nodejs
> No build command found, searching known files
> No build command found, searching known files
> No build command found, searching known files
> No build command found, searching known files
> No build command found, searching known files
> No build command found, searching known files
> No build command found, searching known files
>dh_auto_test --buildsystem=nodejs
>   ln -s ../. node_modules/tape
>   /bin/sh -ex debian/tests/pkg-js/test
> + + lsgrep -v -f debian/tests/tests_excluded
>  test/add-subtest-async.js test/anonymous-fn.js test/array.js 
> test/async-await.js test/bound.js test/child_ordering.js 
> test/circular-things.js test/comment.js test/common.js 
> test/create_multiple_streams.js test/deep-equal-failure.js test/deep.js 
> test/default-messages.js test/double_end.js test/edge-cases.js 
> test/end-as-callback.js test/error.js test/exit.js test/exposed-harness.js 
> test/fail.js test/has spaces.js test/ignore_from_gitignore.js test/import.js 
> test/many.js test/match.js test/max_listeners.js 
> test/nested-async-plan-noend.js test/nested-sync-noplan-noend.js 
> test/nested.js test/nested2.js test/no_callback.js test/no_only.js 
> test/not-deep-equal-failure.js test/not-equal-failure.js test/numerics.js 
> test/objectMode.js test/objectModeWithComment.js test/onFailure.js 
> test/onFinish.js test/only-twice.js test/only.js test/only2.js test/only3.js 
> test/only4.js test/only5.js test/order.js test/plan_optional.js 
> test/promise_fail.js test/require.js test/skip.js test/skip_explanation.js 
> test/stackTrace.js test/subcount.js test/subtest_and_async.js 
> test/subtest_plan.js test/teardown.js test/throws.js test/timeout.js 
> test/timeoutAfter.js test/todo.js test/todo_explanation.js 
> test/todo_single.js test/too_many.js test/undef.js
> + tap -J test/add-subtest-async.js test/anonymous-fn.js test/array.js 
> test/bound.js test/child_ordering.js test/circular-things.js test/comment.js 
> test/common.js test/create_multiple_streams.js test/deep.js 
> test/default-messages.js test/double_end.js test/edge-cases.js 
> test/end-as-callback.js test/error.js test/exposed-harness.js test/fail.js 
> test/has spaces.js test/ignore_from_gitignore.js test/import.js test/many.js 
> test/match.js test/max_listeners.js test/nested-async-plan-noend.js 
> test/nested-sync-noplan-noend.js test/nested.js test/nested2.js 
> test/no_callback.js test/no_only.js test/numerics.js test/objectMode.js 
> test/objectModeWithComment.js test/onFailure.js test/onFinish.js 
> test/only-twice.js test/only.js test/only2.js test/only3.js test/only4.js 
> test/only5.js test/order.js test/plan_optional.js test/promise_fail.js 
> test/require.js test/skip.js test/skip_explanation.js test/subcount.js 
> test/subtest_and_async.js test/subtest_plan.js test/throws.js test/timeout.js 
> test/timeoutAfter.js test/todo.js test/todo_explanation.js 
> test/todo_single.js test/undef.js
> TAP version 13
> (node:1647734) DeprecationWarning: deepEqual() is deprecated, use same() 
> instead
> (Use `node --trace-deprecation ...` to show where the warning was created)
> Since Acorn 8.0.0, options.ecmaVersion is required.
> Defaulting to 2020, but this will stop working in the future.
> ok 1 - test/add-subtest-async.js # time=2996.169ms {
> # parent
> ok 1 parent
> (node:1647732) DeprecationWarning: deepEqual() is deprecated, use same() 
> instead
> (Use `node --trace-deprecation ...` to show where the warning was created)
> # child
> ok 2 child
> 
> 1..2
> # tests 2
> # pass  2
> 
> # ok
> }
> 
> ok 2 - test/anonymous-fn.js # time=36.466ms {
> # Subtest: inside anonymous functions
> 1..1
> ok 1 - should be equivalent
> ok 1 - inside anonymous functions # time=30.903ms
> 
> 1..1
> # time=36.466ms
> }
> 
> ok 3 - test/array.js # time=67.485ms {
> # Subtest: array test

Bug#1009586: node-trysound-sax: FTBFS: ERROR: Coverage for statements (79.38%) does not meet global threshold (100%)

[Lucas Nussbaum]

Source: node-trysound-sax
Version: 0.2.0-2
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 build
> dh build
>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/\@trysound
>   ln -s ../../. node_modules/\@trysound/sax
>   /bin/sh -ex debian/tests/pkg-js/test
> + tap test/attribute-name.js test/attribute-no-space.js 
> test/attribute-unquoted.js test/bom.js test/buffer-overrun.js test/case.js 
> test/cdata-chunked.js test/cdata-end-split.js test/cdata-fake-end.js 
> test/cdata-multiple.js test/cdata.js test/cyrillic.js 
> test/duplicate-attribute.js test/emoji.js test/entities.js 
> test/entity-mega.js test/entity-nan.js test/entity-tags.js test/flush.js 
> test/index.js test/issue-23.js test/issue-30.js test/issue-35.js 
> test/issue-47.js test/issue-49.js test/issue-84.js test/issue-86.js 
> test/not-string.js test/opentagstart.js test/parser-position.js 
> test/script-close-better.js test/script.js test/self-closing-child-strict.js 
> test/self-closing-child.js test/self-closing-tag.js 
> test/stand-alone-comment.js test/stray-ending.js 
> test/trailing-attribute-no-value.js test/trailing-non-whitespace.js 
> test/unclosed-root.js test/unquoted.js test/xml-internal-entities.js 
> test/xml_entities.js test/xmlns-as-tag-name.js test/xmlns-issue-41.js 
> test/xmlns-rebinding.js test/xmlns-strict.js test/xmlns-unbound-element.js 
> test/xmlns-unbound.js test/xmlns-xml-default-ns.js 
> test/xmlns-xml-default-prefix-attribute.js test/xmlns-xml-default-prefix.js 
> test/xmlns-xml-default-redefine.js --cov -j4
> TAP version 13
> (node:1125840) DeprecationWarning: deepEqual() is deprecated, use same() 
> instead
> (Use `node --trace-deprecation ...` to show where the warning was created)
> ok 1 - test/attribute-name.js # time=21.97ms {
> ok 1 - no unexpected events
> ok 2 - should be equal
> ok 3 - should be equivalent
> ok 4 - no unexpected events
> ok 5 - should be equal
> ok 6 - should be equivalent
> ok 7 - no unexpected events
> ok 8 - should be equal
> ok 9 - should be equivalent
> ok 10 - no unexpected events
> ok 11 - should be equal
> ok 12 - should be equivalent
> 1..12
> # time=21.97ms
> }
> 
> (node:1125843) DeprecationWarning: deepEqual() is deprecated, use same() 
> instead
> (Use `node --trace-deprecation ...` to show where the warning was created)
> (node:1125842) DeprecationWarning: deepEqual() is deprecated, use same() 
> instead
> (Use `node --trace-deprecation ...` to show where the warning was created)
> (node:1125841) DeprecationWarning: deepEqual() is deprecated, use same() 
> instead
> (Use `node --trace-deprecation ...` to show where the warning was created)
> ok 2 - test/attribute-no-space.js # time=31.097ms {
> ok 1 - no unexpected events
> ok 2 - should be equal
> ok 3 - should be equivalent
> ok 4 - no unexpected events
> ok 5 - should be equal
> ok 6 - should be equivalent
> ok 7 - no unexpected events
> ok 8 - should be equal
> ok 9 - should be equivalent
> ok 10 - no unexpected events
> ok 11 - should be equal
> ok 12 - should be equivalent
> ok 13 - no unexpected events
> ok 14 - should be equal
> ok 15 - should be equivalent
> ok 16 - no unexpected events
> ok 17 - should be equal
> ok 18 - should be equivalent
> ok 19 - no unexpected events
> ok 20 - should be equal
> ok 21 - should be equivalent
> ok 22 - no unexpected events
> ok 23 - should be equal
> ok 24 - should be equal
> ok 25 - no unexpected events
> ok 26 - should be equal
> ok 27 - should be equivalent
> ok 28 - no unexpected events
> ok 29 - should be equal
> ok 30 - should be equivalent
> ok 31 - no unexpected events
> ok 32 - should be equal
> ok 33 - should be equivalent
> ok 34 - no unexpected events
> ok 35 - should be equal
> ok 36 - should be equivalent
> ok 37 - no unexpected events
> ok 38 - should be equal
> ok 39 - should be equivalent
> ok 40 - no unexpected events
> ok 41 - should be equal
> ok 42 - should be equivalent
> ok 43 - no unexpected events
> ok 44 - should be equal
> ok 45 - should be equivalent
> ok 46 - no unexpected events
&g

Bug#1009584: node-extend: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1

[Lucas Nussbaum]

Source: node-extend
Version: 3.0.2+~3.0.1-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
> Link node_modules/@types/extend -> ../../types-extend
>dh_auto_build --buildsystem=nodejs
> No build command found, searching known files
> No build command found, searching known files
>dh_auto_test --buildsystem=nodejs
>   ln -s ../. node_modules/extend
>   /bin/sh -ex debian/tests/pkg-js/test
> + tap test.js
> TAP version 13
> not ok 1 - test.js # time=22.434ms {
> not ok 1 - ENOENT: no such file or directory, stat 'test.js'
>   ---
>   stack: |
> runAllFiles (/usr/share/nodejs/tap/bin/run.js:652:15)
> runTests (/usr/share/nodejs/tap/bin/run.js:783:3)
> mainAsync (/usr/share/nodejs/tap/bin/run.js:267:5)
> main (/usr/share/nodejs/tap/bin/run.js:141:3)
> Object.j.main (/usr/share/nodejs/jackspeak/index.js:483:5)
> execute (/usr/share/nodejs/jackspeak/index.js:224:7)
> jack (/usr/share/nodejs/jackspeak/index.js:163:31)
> module.exports (/usr/share/nodejs/tap/bin/jack.js:28:26)
> Object. (/usr/share/nodejs/tap/bin/run.js:874:23)
>   at:
> line: 1131
> column: 3
> file: fs.js
> function: Object.statSync
>   errno: -2
>   syscall: stat
>   code: ENOENT
>   path: test.js
>   test: test.js
>   ...
> 
> 1..1
> # failed 1 test
> }
> 
> 1..1
> # failed 1 test
> # time=55.101ms
> --|-|--|-|-|---
> File  | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s 
> --|-|--|-|-|---
> All files |   0 |0 |   0 |   0 |   
> --|-|--|-|-|---
> 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-extend_3.0.2+~3.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=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.

Bug#1009588: node-config-chain: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1

[Lucas Nussbaum]

Source: node-config-chain
Version: 1.1.12-2
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/config-chain
>   /bin/sh -ex debian/tests/pkg-js/test
> + tap test/
> TAP version 13
> not ok 1 - test/ # time=21.473ms {
> not ok 1 - ENOENT: no such file or directory, stat 'test/'
>   ---
>   stack: |
> runAllFiles (/usr/share/nodejs/tap/bin/run.js:652:15)
> runTests (/usr/share/nodejs/tap/bin/run.js:783:3)
> mainAsync (/usr/share/nodejs/tap/bin/run.js:267:5)
> main (/usr/share/nodejs/tap/bin/run.js:141:3)
> Object.j.main (/usr/share/nodejs/jackspeak/index.js:483:5)
> execute (/usr/share/nodejs/jackspeak/index.js:224:7)
> jack (/usr/share/nodejs/jackspeak/index.js:163:31)
> module.exports (/usr/share/nodejs/tap/bin/jack.js:28:26)
> Object. (/usr/share/nodejs/tap/bin/run.js:874:23)
>   at:
> line: 1131
> column: 3
> file: fs.js
> function: Object.statSync
>   errno: -2
>   syscall: stat
>   code: ENOENT
>   path: test/
>   test: test/
>   ...
> 
> 1..1
> # failed 1 test
> }
> 
> 1..1
> # failed 1 test
> # time=45.507ms
> --|-|--|-|-|---
> File  | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s 
> --|-|--|-|-|---
> All files |   0 |0 |   0 |   0 |   
> --|-|--|-|-|---
> 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-config-chain_1.1.12-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=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.

Bug#1009585: node-fd-slicer: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 3

[Lucas Nussbaum]

Source: node-fd-slicer
Version: 1.1.0+repack1-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 ../debian/tests/test_modules/stream-equal 
> node_modules/stream-equal
>   ln -s ../debian/tests/test_modules/streamsink node_modules/streamsink
>   ln -s ../. node_modules/fd-slicer
>   /bin/sh -ex debian/tests/pkg-js/test
> + mocha --check-leaks --timeout 1
> 
> 
>   FdSlicer
> (node:3356748) [DEP0005] DeprecationWarning: Buffer() is deprecated due to 
> security and usability issues. Please use the Buffer.alloc(), 
> Buffer.allocUnsafe(), or Buffer.from() methods instead.
> (Use `node --trace-deprecation ...` to show where the warning was created)
> undefined reads a 20MB file (autoClose on) (253ms)
> undefined reads 4 chunks simultaneously (216ms)
> undefined writes a 20MB file (autoClose on) (143ms)
> undefined writes 4 chunks simultaneously (128ms)
> undefined throws on invalid ref
> 1) write stream emits error when max size exceeded
> undefined write stream does not emit error when max size not exceeded
> 2) write stream start and end work together
> undefined write stream emits progress events
> undefined write stream unrefs when destroyed
> undefined read stream unrefs when destroyed
> undefined fdSlicer.read
> undefined fdSlicer.write
> 
>   BufferSlicer
> undefined invalid ref
> undefined read and write
> undefined createReadStream
> 3) createWriteStream exceed buffer size
> undefined createWriteStream ok
> 
> 
>   15 passing (31s)
>   3 failing
> 
>   1) FdSlicer
>write stream emits error when max size exceeded:
>  Error: Timeout of 1ms exceeded. For async tests and hooks, ensure 
> "done()" is called; if returning a Promise, ensure it resolves. 
> (/<>/test/test.js)
>   at createTimeoutError (/usr/share/nodejs/mocha/lib/errors.js:498:15)
>   at Test.Runnable._timeoutError 
> (/usr/share/nodejs/mocha/lib/runnable.js:431:10)
>   at Timeout. (/usr/share/nodejs/mocha/lib/runnable.js:246:24)
>   at listOnTimeout (internal/timers.js:557:17)
>   at processTimers (internal/timers.js:500:7)
> 
>   2) FdSlicer
>write stream start and end work together:
>  Error: Timeout of 1ms exceeded. For async tests and hooks, ensure 
> "done()" is called; if returning a Promise, ensure it resolves. 
> (/<>/test/test.js)
>   at createTimeoutError (/usr/share/nodejs/mocha/lib/errors.js:498:15)
>   at Test.Runnable._timeoutError 
> (/usr/share/nodejs/mocha/lib/runnable.js:431:10)
>   at Timeout. (/usr/share/nodejs/mocha/lib/runnable.js:246:24)
>   at listOnTimeout (internal/timers.js:557:17)
>   at processTimers (internal/timers.js:500:7)
> 
>   3) BufferSlicer
>createWriteStream exceed buffer size:
>  Error: Timeout of 1ms exceeded. For async tests and hooks, ensure 
> "done()" is called; if returning a Promise, ensure it resolves. 
> (/<>/test/test.js)
>   at createTimeoutError (/usr/share/nodejs/mocha/lib/errors.js:498:15)
>   at Test.Runnable._timeoutError 
> (/usr/share/nodejs/mocha/lib/runnable.js:431:10)
>   at Timeout. (/usr/share/nodejs/mocha/lib/runnable.js:246:24)
>   at listOnTimeout (internal/timers.js:557:17)
>   at processTimers (internal/timers.js:500:7)
> 
> 
> 
> dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 3


The full build log is available from:
http://qa-logs.debian.net/2022/04/12/node-fd-slicer_1.1.0+repack1-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.

Bug#1009582: node-follow-redirects: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1

[Lucas Nussbaum]

Source: node-follow-redirects
Version: 1.14.9+~1.14.1-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
> Link node_modules/@types/follow-redirects -> ../../types-follow-redirects
>dh_auto_build --buildsystem=nodejs
> No build command found, searching known files
> No build command found, searching known files
>dh_auto_test --buildsystem=nodejs
>   ln -s ../. node_modules/follow-redirects
>   /bin/sh -ex debian/tests/pkg-js/test
> + mocha
> 
> 
>   follow-redirects
> undefined http.get with string and callback - redirect (47ms)
> undefined http.get with URL object and callback - redirect
> undefined http.get with options object and callback - redirect
> undefined http.get with string and callback - no redirect
> undefined http.get with options object and callback - no redirect
> undefined http.get with host option and callback - redirect
> undefined http.get with response event
> undefined should return with the original status code if the response 
> does not contain a location header
> undefined should emit connection errors on the returned stream
> undefined should emit socket events on the returned stream
> undefined should emit connect events on the returned stream
> undefined emits an error on redirects with an invalid location
> undefined emits an error whem url.resolve fails
> undefined emits an error when the request fails for another reason
> undefined should destroy responses
> undefined should honor query params in redirects
> undefined should allow aborting
> undefined should provide connection
> undefined should provide flushHeaders
> undefined should provide getHeader
> undefined should provide removeHeader
> undefined should provide setHeader
> undefined should provide setNoDelay
> undefined should provide setSocketKeepAlive
> undefined should provide setTimeout
> undefined should provide socket
> undefined should wait for an explicit call to end
> undefined errors on write after end
> undefined should support writing into request stream without redirects
> undefined should support writing into request stream with redirects
> undefined should support piping into request stream without redirects
> undefined should support piping into request stream with redirects
> undefined should support piping into request stream with explicit 
> Content-Length without redirects
> undefined should support piping into request stream with explicit 
> Content-Length with redirects
> undefined keeps the header when redirected from HTTP to HTTPS
> undefined drops the header when redirected from HTTPS to HTTP
> undefined keeps the header when redirected from HTTP to HTTPS
> undefined drops the header when redirected from HTTPS to HTTP
> setTimeout
>   undefined clears timeouts after a successful response
>   undefined clears timeouts after an error response
>   undefined handles errors occuring before a socket is established
>   undefined sets a timeout when the socket already exists
>   undefined destroys the socket after configured inactivity period (102ms)
>   undefined should timeout on the final request
>   undefined should include redirect delays in the timeout
>   undefined overrides existing timeouts
> should obey a `maxRedirects` property
>   undefined which defaults to 21 (64ms)
>   undefined which can be set globally
>   undefined set as an option on an individual request
> the trackRedirects option
>   when not set
> undefined should not track redirects
>   when set to true
> 1) should track redirects
> should switch to safe methods when appropriate
>   when redirecting with status code 300
> undefined should reuse GET
> undefined should reuse HEAD
> undefined should reuse POST
> undefined should reuse PUT
> undefined should reuse DELETE
>   when redirecting with status code 301
> undefined should reuse GET
> undefined should reuse HEAD
> undefined should switch from POST to GET
> undefined should reuse PUT
> undefined should reuse DELETE
>   when redirecting with status code 302
> undefined should reuse GET
> undefined should reuse HEAD
> undefi

Bug#1009583: node-difflet: FTBFS: ERROR: Coverage for statements (74.82%) does not meet global threshold (100%)

[Lucas Nussbaum]

Source: node-difflet
Version: 1.0.1-3
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 ../debian/tests/test_modules/ent node_modules/ent
>   ln -s ../. node_modules/difflet
>   /bin/sh -ex debian/tests/pkg-js/test
> + tap -J test/diffing-NaN.js test/html.js test/object_tests.js
> TAP version 13
> (node:525363) [DEP0005] DeprecationWarning: Buffer() is deprecated due to 
> security and usability issues. Please use the Buffer.alloc(), 
> Buffer.allocUnsafe(), or Buffer.from() methods instead.
> (Use `node --trace-deprecation ...` to show where the warning was created)
> ok 1 - test/diffing-NaN.js # time=22.16ms {
> # Subtest: diffing NaN against NaN
> 1..1
> ok 1 - should be equal
> ok 1 - diffing NaN against NaN # time=6.605ms
> 
> # Subtest: diffing { o: NaN } against { o: NaN }
> 1..1
> ok 1 - should be equal
> ok 2 - diffing { o: NaN } against { o: NaN } # time=2.104ms
> 
> 1..2
> # time=22.16ms
> }
> 
> (node:525362) [DEP0005] DeprecationWarning: Buffer() is deprecated due to 
> security and usability issues. Please use the Buffer.alloc(), 
> Buffer.allocUnsafe(), or Buffer.from() methods instead.
> (Use `node --trace-deprecation ...` to show where the warning was created)
> ok 2 - test/html.js # time=23.063ms {
> # Subtest: html output
> 1..1
> ok 1 - should be equal
> ok 1 - html output # time=15.411ms
> 
> # Subtest: compare html output
> 1..1
> ok 1 - should be equal
> ok 2 - compare html output # time=2.394ms
> 
> 1..2
> # time=23.063ms
> }
> 
> ok 3 - test/object_tests.js # time=30.609ms {
> # Subtest: diffing with empty nested array
> 1..1
> ok 1 - should be equal
> ok 1 - diffing with empty nested array # time=10.307ms
> 
> # Subtest: diffing nested array with missing values
> 1..1
> ok 1 - should be equal
> ok 2 - diffing nested array with missing values # time=1.956ms
> 
> # Subtest: diffing nested array with added values
> 1..1
> ok 1 - should be equal
> ok 3 - diffing nested array with added values # time=7.705ms
> 
> 1..3
> # time=30.609ms
> }
> 
> 1..3
> # time=1474.384ms
> ERROR: Coverage for lines (76.51%) does not meet global threshold (100%)
> ERROR: Coverage for functions (80%) does not meet global threshold (100%)
> ERROR: Coverage for branches (64.41%) does not meet global threshold (100%)
> ERROR: Coverage for statements (74.82%) does not meet global threshold (100%)
> ---|-|--|-|-|---
> File   | % Stmts | % Branch | % Funcs | % 
> Lines | Uncovered Line #s 
> ---|-|--|-|-|---
> All files  |   74.82 |64.41 |  80 |   
> 76.51 |   
>  node-difflet-1.0.1|   77.07 |65.89 |   88.23 |   
> 79.22 |   
>   index.js |   77.07 |65.89 |   88.23 |   
> 79.22 | ...49,367,376,379 
>  0.1/debian/tests/test_modules/ent |   57.57 |47.82 |   33.33 |   
> 57.57 |   
>   index.js |   57.57 |47.82 |   33.33 |   
> 57.57 | 13,26,35-59   
> ---|-|--|-|-|---
> 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-difflet_1.0.1-3_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.

Bug#1009581: node-zrender: FTBFS: @rollup/plugin-typescript TS2322: Type 'string' is not assignable to type 'GlobalCompositeOperation'.

[Lucas Nussbaum]

Source: node-zrender
Version: 5.3.1+dfsg-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
> Link ./node_modules/@rollup/plugin-typescript -> 
> /usr/share/nodejs/@rollup/plugin-typescript
> Link ./node_modules/tslib -> /usr/share/nodejs/tslib
> Link ./node_modules/typescript -> /usr/share/nodejs/typescript
> Link ./node_modules/@types/node -> /usr/share/nodejs/@types/node
> Copy /usr/share/nodejs/jest-diff -> ./node_modules/
> Copy /usr/share/nodejs/pretty-format -> ./node_modules/
> Copy /usr/share/nodejs/ts-jest -> ./node_modules/
> Copy /usr/share/nodejs/@types/jest -> ./node_modules/@types
>dh_auto_build --buildsystem=nodejs
> Found debian/nodejs/./build
>   cd ./. && sh -ex debian/nodejs/./build
> + set -e
> + node build/build.js --minify
> @rollup/plugin-typescript TS2322: Type 'string' is not assignable to type 
> 'GlobalCompositeOperation'.
> [1/0]: index.ts
> [2/0]: src/all.ts
> [3/0]: src/zrender.ts
> [4/0]: src/export.ts
> [5/0]: src/canvas/Painter.ts
> [6/0]: src/svg/Painter.ts
> [7/0]: src/core/env.ts
> [8/0]: src/core/util.ts
> [9/0]: src/Handler.ts
> [10/0]: src/Storage.ts
> [11/0]: src/animation/Animation.ts
> [12/0]: src/dom/HandlerProxy.ts
> [13/0]: src/tool/color.ts
> [14/0]: src/config.ts
> [15/0]: src/graphic/Group.ts
> [16/0]: src/core/matrix.ts
> [17/0]: src/core/vector.ts
> [18/0]: src/tool/path.ts
> [19/0]: src/tool/parseSVG.ts
> [20/0]: src/tool/morphPath.ts
> [21/0]: src/core/Point.ts
> [22/0]: src/Element.ts
> [23/0]: src/graphic/Displayable.ts
> [24/0]: src/graphic/Path.ts
> [25/0]: src/graphic/Image.ts
> [26/0]: src/graphic/CompoundPath.ts
> [27/0]: src/graphic/TSpan.ts
> [28/0]: src/graphic/IncrementalDisplayable.ts
> [29/0]: src/graphic/Text.ts
> [30/0]: src/graphic/shape/Arc.ts
> [31/0]: src/graphic/shape/BezierCurve.ts
> [32/0]: src/graphic/shape/Circle.ts
> [33/0]: src/graphic/shape/Droplet.ts
> [34/0]: src/graphic/shape/Ellipse.ts
> [35/0]: src/graphic/shape/Heart.ts
> [36/0]: src/graphic/shape/Isogon.ts
> [37/0]: src/graphic/shape/Line.ts
> [38/0]: src/graphic/shape/Polygon.ts
> [39/0]: src/graphic/shape/Polyline.ts
> [40/0]: src/graphic/shape/Rect.ts
> [41/0]: src/graphic/shape/Ring.ts
> [42/0]: src/graphic/shape/Rose.ts
> [43/0]: src/graphic/shape/Sector.ts
> [44/0]: src/graphic/shape/Star.ts
> [45/0]: src/graphic/shape/Trochoid.ts
> [46/0]: src/graphic/LinearGradient.ts
> [47/0]: src/graphic/RadialGradient.ts
> [48/0]: src/graphic/Pattern.ts
> [49/0]: src/core/BoundingRect.ts
> [50/0]: src/core/OrientedBoundingRect.ts
> [51/0]: src/debug/showDebugDirtyRect.ts
> [52/0]: src/core/platform.ts
> [53/0]: src/canvas/Layer.ts
> [54/0]: src/animation/requestAnimationFrame.ts
> [55/0]: src/canvas/graphic.ts
> [56/0]: src/graphic/constants.ts
> [57/0]: src/canvas/helper.ts
> [58/0]: src/svg/graphic.ts
> [59/0]: src/svg/core.ts
> [60/0]: src/svg/helper.ts
> [61/0]: src/svg/patch.ts
> [62/0]: src/mixin/Draggable.ts
> [63/0]: src/core/Eventful.ts
> [64/0]: src/core/event.ts
> [65/0]: src/core/GestureMgr.ts
> [66/0]: src/core/timsort.ts
> [67/0]: src/animation/Animator.ts
> [68/0]: src/core/LRU.ts
> [69/0]: src/core/PathProxy.ts
> [70/0]: src/tool/transformPath.ts
> [71/0]: src/tool/parseXML.ts
> [72/0]: src/core/curve.ts
> [73/0]: src/core/Transformable.ts
> [74/0]: src/tool/dividePath.ts
> [75/0]: src/tool/convertPath.ts
> [76/0]: src/contain/text.ts
> [77/0]: src/contain/path.ts
> [78/0]: src/graphic/helper/parseText.ts
> [79/0]: src/graphic/helper/subPixelOptimize.ts
> [80/0]: src/graphic/helper/poly.ts
> [81/0]: src/graphic/helper/roundRect.ts
> [82/0]: src/graphic/helper/roundSector.ts
> [83/0]: src/graphic/Gradient.ts
> [84/0]: src/graphic/helper/image.ts
> [85/0]: src/canvas/dashStyle.ts
> [86/0]: src/svg/SVGPathRebuilder.ts
> [87/0]: src/svg/mapStyleToAttrs.ts
> [88/0]: src/svg/cssAnimation.ts
> [89/0]: src/svg/domapi.ts
> [90/0]: src/core/dom.ts
> [91/0]: src/animation/Clip.ts
> [92/0]: src/animation/easing.ts
> [93/0]: src/animation/cubicEasing.ts
> [94/0]: src/core/bbox.ts
> [95/0]: src/contain/line.ts
> [96/0]: src/contain/cubic.ts
> [97/0]: src/contain/quadratic.ts
> [98/0]: src/contain/arc.ts
> [99/0]: src/contain/windingLine.ts
> [100/0]: src/graphic/helper/smoothBezier.ts
> [101/0]: src/core/fourPointsTransform.ts
> [102/0

Bug#1009580: node-inline-source-map: FTBFS: ERROR: Coverage for statements (98.18%) does not meet global threshold (100%)

[Lucas Nussbaum]

Source: node-inline-source-map
Version: 0.6.2~git-6
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/inline-source-map
>   /bin/sh -ex debian/tests/pkg-js/test
> + tap test/inline-source-map.js test/source-content.js
> TAP version 13
> (node:123364) DeprecationWarning: deepEqual() is deprecated, use same() 
> instead
> (Use `node --trace-deprecation ...` to show where the warning was created)
> (node:123363) DeprecationWarning: deepEqual() is deprecated, use same() 
> instead
> (Use `node --trace-deprecation ...` to show where the warning was created)
> ok 1 - test/inline-source-map.js # time=64.03ms {
> # Subtest: generated mappings
> # Subtest: one file no offset
> ok 1 - generates correct mappings
> ok 2 - encodes generated mappings
> ok 3 - returns correct inline mapping url
> 1..3
> ok 1 - one file no offset # time=11.982ms
> 
> # Subtest: two files no offset
> ok 1 - generates correct mappings
> ok 2 - encodes generated mappings
> ok 3 - returns correct inline mapping url
> 1..3
> ok 2 - two files no offset # time=3.628ms
> 
> # Subtest: one line source
> ok 1 - generates correct mappings
> 1..1
> ok 3 - one line source # time=1.095ms
> 
> # Subtest: with offset
> ok 1 - generates correct mappings
> ok 2 - encodes generated mappings with offset
> 1..2
> ok 4 - with offset # time=2.727ms
> 
> 1..4
> ok 1 - generated mappings # time=38.512ms
> 
> # Subtest: given mappings, with one having no original
> # Subtest: no offset
> ok 1 - adds correct mappings
> ok 2 - encodes generated mappings
> ok 3 - returns correct inline mapping url
> 1..3
> ok 1 - no offset # time=2.163ms
> 
> # Subtest: with offset
> ok 1 - adds correct mappings
> ok 2 - encodes mappings with offset
> 1..2
> ok 2 - with offset # time=2.028ms
> 
> 1..2
> ok 2 - given mappings, with one having no original # time=11.728ms
> 
> # Subtest: inline mapping url with charset opt
> # Subtest: set inline mapping url charset to gbk
> ok 1 - charset set to gbk
> 1..1
> ok 1 - set inline mapping url charset to gbk # time=0.688ms
> 
> # Subtest: default charset should be utf-8
> ok 1 - charset default to utf-8
> 1..1
> ok 2 - default charset should be utf-8 # time=0.676ms
> 
> 1..2
> ok 3 - inline mapping url with charset opt # time=6.088ms
> 
> 1..3
> # time=64.03ms
> }
> 
> ok 2 - test/source-content.js # time=45.324ms {
> # Subtest: generated mappings
> # Subtest: one file with source content
> ok 1 - includes source content
> ok 2 - encodes generated mappings including source content
> ok 3 - returns correct inline mapping url including source content
> 1..3
> ok 1 - one file with source content # time=10.565ms
> 
> # Subtest: two files with source content
> ok 1 - includes source content for both files
> ok 2 - encodes generated mappings including source content
> ok 3 - returns correct inline mapping url including source content
> 1..3
> ok 2 - two files with source content # time=5.413ms
> 
> # Subtest: two files, only one with source content
> ok 1 - includes source content for the file with source content 
> and [null] for the other file
> ok 2 - encodes generated mappings including source content
> ok 3 - returns correct inline mapping url including source content
> 1..3
> ok 3 - two files, only one with source content # time=2.8ms
> 
> # Subtest: one file with empty source
> ok 1 - should be equivalent
> 1..1
>

Bug#1009579: node-qs: FTBFS: Error: module util in /<>/node_modules/object-inspect not found

[Lucas Nussbaum]

Source: node-qs
Version: 6.10.3+ds+~6.9.7-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):
> make[1]: Entering directory '/<>'
> dh_auto_build
> mkdir dist
> browserify-lite ./lib/index.js --outfile dist/qs.js
> /usr/share/nodejs/browserify-lite/cli.js:29
>   if (err) throw err;
>^
> 
> Error: module util in /<>/node_modules/object-inspect not found
> at trySearchPath (/usr/share/nodejs/browserify-lite/index.js:269:32)
> at /usr/share/nodejs/browserify-lite/index.js:274:7
> at /usr/share/nodejs/browserify-lite/index.js:294:21
> at FSReqCallback.oncomplete (fs.js:191:21)
> make[1]: *** [debian/rules:13: override_dh_auto_build] Error 1


The full build log is available from:
http://qa-logs.debian.net/2022/04/12/node-qs_6.10.3+ds+~6.9.7-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.

Bug#1009578: node-uvu: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1

[Lucas Nussbaum]

Source: node-uvu
Version: 0.5.3+~cs4.10.3-4
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):
> make[1]: Entering directory '/<>'
> dh_auto_build --buildsystem=nodejs
> Found debian/nodejs/mri/build
>   cd ./mri && sh -ex ../debian/nodejs/mri/build
> + bundt
> 
> Filename Filesize  (gzip)
> lib/index.js  1.67 kB  790 B 
> lib/index.mjs 1.67 kB  783 B 
> 
> Found debian/nodejs/dequal/build
>   cd ./dequal && sh -ex ../debian/nodejs/dequal/build
> + bundt
> 
> Lite Filesize  (gzip)
> lite/index.js  487 B   304 B 
> lite/index.mjs 493 B   302 B 
> lite/index.min.js  655 B   370 B 
> 
> 
> Default  Filesize  (gzip)
> dist/index.js 1.09 kB  489 B 
> dist/index.mjs1.11 kB  486 B 
> dist/index.min.js 1.26 kB  558 B 
> 
> Found debian/nodejs/sade/build
>   cd ./sade && sh -ex ../debian/nodejs/sade/build
> + rollup -c
> 
> src/index.js → lib/index.mjs, lib/index.js...
> created lib/index.mjs, lib/index.js in 353ms
> bundt
> 
> Diff   Filesize   (gzip)
> diff/index.js   3.27 kB  1.49 kB
> diff/index.mjs  3.33 kB  1.47 kB
> diff/index.d.ts  337 B134 B 
> 
> 
> Parse   Filesize  (gzip)
> parse/index.js972 B   593 B 
> parse/index.mjs   986 B   600 B 
> parse/index.d.ts  441 B   253 B 
> 
> 
> Assert   Filesize   (gzip)
> assert/index.js   3.62 kB  1.17 kB
> assert/index.mjs  3.62 kB  1.19 kB
> assert/index.d.ts 1.92 kB   459 B 
> 
> 
> Default   Filesize   (gzip)
> dist/index.js  2.91 kB  1.54 kB
> dist/index.mjs 2.91 kB  1.53 kB
> index.d.ts  757 B335 B 
> 
> mjs2cjs dist/index.mjs
> 
> dist/index.mjs → index.cjs...
> (!) Unresolved dependencies
> https://rollupjs.org/guide/en/#warning-treating-module-as-external-dependency
> uvu/diff (imported by dist/index.mjs)
> created index.cjs in 62ms
> help2man --version-string `node bin.js -v|sed -s 's/uvu, //'` \
> -n 'Extremely fast and lightweight test runner for Node.js and the browser' \
> -N ./bin.js >uvu.1
> perl -i -pe 's/bin\.js/uvu/g;s/BIN\.JS/UVU/g' uvu.1
> make[1]: Leaving directory '/<>'
>dh_auto_test --buildsystem=nodejs
>   ln -s ../debian/tests/test_modules/esm node_modules/esm
>   ln -s ../debian/tests/test_modules/module-alias 
> node_modules/module-alias
>   ln -s ../debian/tests/test_modules/totalist node_modules/totalist
>   ln -s ../. node_modules/uvu
>   /bin/sh -ex debian/tests/pkg-js/test
> + ./bin.js test index.js
> [FAIL] assert.js :: "run w/o error code"
> [FAIL] diff.js :: "run w/o error code"
> [FAIL] parse.js :: "run w/o error code"
> [FAIL] suite.js :: "run w/o error code"
> [FAIL] uvu.js :: "run w/o error code"
> 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-uvu_0.5.3+~cs4.10.3-4_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.

Bug#1009577: node-browser-unpack: FTBFS: ERROR: Coverage for statements (80.32%) does not meet global threshold (100%)

[Lucas Nussbaum]

Source: node-browser-unpack
Version: 1.4.2-3
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
>   install -d /<>/debian/.debhelper/generated/_source/home
>dh_auto_build --buildsystem=nodejs
> No build command found, searching known files
>dh_auto_test --buildsystem=nodejs
>   test -e node_modules
>   mkdir -p node_modules
>   ln -s ../. node_modules/browser-unpack
>   /bin/sh -ex debian/tests/pkg-js/test
> + tap -R spec test/assignment.js test/empty-statements.js test/multi-byte.js 
> test/return.js test/standalone.js test/uglified.js test/unpack.js
> 
> test/assignment.js
> 
>   ✓ should unpack 3 rows
> 
>   ✓ should not throw
> test/empty-statements.js
> 
>   ✓ should unpack 3 rows
> 
>   ✓ should not throw
> test/multi-byte.js
> 
>   ✓ should unpack the same number of rows
> 
>   ✓ should unpack 3 rows
> 
>   ✓ should have the same source
> 
>   ✓ should have the same source
> 
>   ✓ should have the same source
> 
>   ✓ should not throw
> test/return.js
> 
>   ✓ should be strictly equal
> test/standalone.js
> 
>   ✓ should unpack 3 rows
> 
>   ✓ should not throw
> test/uglified.js
> 
>   ✓ should unpack 3 rows
> 
>   ✓ should not throw
> 
>   ✓ should be deeply equivalent
> test/unpack.js
> 
>   ✓ should be strictly equal
> 
>   ✓ did not emit an error
> 
>   18 passing (1s)
> ERROR: Coverage for branches (70.45%) does not meet global threshold (100%)
> ERROR: Coverage for statements (80.32%) does not meet global threshold (100%)
> --|-|--|-|-|---
> File  | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s 
> --|-|--|-|-|---
> All files |   80.32 |70.45 | 100 | 100 |   
>  index.js |   80.32 |70.45 | 100 | 100 | 18-19,28-36,75-81 
> --|-|--|-|-|---
>   rm -fr -- /tmp/dh-xdg-rundir-vQcJ2P0I
> 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-browser-unpack_1.4.2-3_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.

Bug#1009576: node-chownr: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1

[Lucas Nussbaum]

Source: node-chownr
Version: 2.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/chownr
>   /bin/sh -ex debian/tests/pkg-js/test
> + tap concurrent-sync.js old-readdir.js
> TAP version 13
> not ok 1 - concurrent-sync.js # time=18.738ms {
> not ok 1 - ENOENT: no such file or directory, stat 'concurrent-sync.js'
>   ---
>   stack: |
> runAllFiles (/usr/share/nodejs/tap/bin/run.js:652:15)
> runTests (/usr/share/nodejs/tap/bin/run.js:783:3)
> mainAsync (/usr/share/nodejs/tap/bin/run.js:267:5)
> main (/usr/share/nodejs/tap/bin/run.js:141:3)
> Object.j.main (/usr/share/nodejs/jackspeak/index.js:483:5)
> execute (/usr/share/nodejs/jackspeak/index.js:224:7)
> jack (/usr/share/nodejs/jackspeak/index.js:163:31)
> module.exports (/usr/share/nodejs/tap/bin/jack.js:28:26)
> Object. (/usr/share/nodejs/tap/bin/run.js:874:23)
>   at:
> line: 1131
> column: 3
> file: fs.js
> function: Object.statSync
>   errno: -2
>   syscall: stat
>   code: ENOENT
>   path: concurrent-sync.js
>   test: concurrent-sync.js
>   ...
> 
> 1..1
> # failed 1 test
> }
> 
> not ok 2 - old-readdir.js # time=5.085ms {
> not ok 1 - ENOENT: no such file or directory, stat 'old-readdir.js'
>   ---
>   stack: |
> runAllFiles (/usr/share/nodejs/tap/bin/run.js:652:15)
> runTests (/usr/share/nodejs/tap/bin/run.js:783:3)
> mainAsync (/usr/share/nodejs/tap/bin/run.js:267:5)
> main (/usr/share/nodejs/tap/bin/run.js:141:3)
> Object.j.main (/usr/share/nodejs/jackspeak/index.js:483:5)
> execute (/usr/share/nodejs/jackspeak/index.js:224:7)
> jack (/usr/share/nodejs/jackspeak/index.js:163:31)
> module.exports (/usr/share/nodejs/tap/bin/jack.js:28:26)
> Object. (/usr/share/nodejs/tap/bin/run.js:874:23)
>   at:
> line: 1131
> column: 3
> file: fs.js
> function: Object.statSync
>   errno: -2
>   syscall: stat
>   code: ENOENT
>   path: old-readdir.js
>   test: old-readdir.js
>   ...
> 
> 1..1
> # failed 1 test
> }
> 
> 1..2
> # failed 2 of 2 tests
> # time=54.135ms
> --|-|--|-|-|---
> File  | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s 
> --|-|--|-|-|---
> All files |   0 |0 |   0 |   0 |   
> --|-|--|-|-|---
> 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-chownr_2.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.

Bug#1009575: node-configstore: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1

[Lucas Nussbaum]

Source: node-configstore
Version: 6.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):
> make[1]: Entering directory '/<>'
> mjs2cjs index.js
> 
> index.js → ./index.cjs...
> (!) Entry module "index.js" is implicitly using "default" export 
> mode, which means for CommonJS output that its default export is assigned to 
> "module.exports". For many tools, such CommonJS output will not be 
> interchangeable with the original ES module. If this is intended, explicitly 
> set "output.exports" to either "auto" or "default", otherwise you might want 
> to consider changing the signature of "index.js" to use named exports 
> only.
> https://rollupjs.org/guide/en/#outputexports
> index.js
> created ./index.cjs in 37ms
> make[1]: Leaving directory '/<>'
>dh_auto_test --buildsystem=nodejs
>   mkdir -p node_modules
>   ln -s ../. node_modules/configstore
>   /bin/sh -ex debian/tests/pkg-js/test
> + set -e
> + mktemp -d
> + HOME=/tmp/tmp.WKFWY7IOID
> + mkdir /tmp/tmp.WKFWY7IOID/.config
> + export HOME
> + jest --ci test.js
> jest-haste-map: Haste module naming collision: configstore
>   The following files share their name; please adjust your hasteImpl:
> * /.pc/export-commonjs-files.patch/package.json
> * /package.json
> 
> FAIL ./test.js
>   ● Test suite failed to run
> 
> Jest encountered an unexpected token
> 
> Jest failed to parse a file. This happens e.g. when your code or its 
> dependencies use non-standard JavaScript syntax, or when Jest is not 
> configured to support such syntax.
> 
> Out of the box Jest supports Babel, which will be used to transform your 
> files into valid JS based on your Babel configuration.
> 
> By default "node_modules" folder is ignored by transformers.
> 
> Here's what you can do:
>  • If you are trying to use ECMAScript Modules, see 
> https://jestjs.io/docs/ecmascript-modules for how to enable it.
>  • If you are trying to use TypeScript, see 
> https://jestjs.io/docs/getting-started#using-typescript
>  • To have some of your "node_modules" files transformed, you can specify 
> a custom "transformIgnorePatterns" in your config.
>  • If you need a custom transformation specify a "transform" option in 
> your config.
>  • If you simply want to mock your non-JS modules (e.g. binary assets) 
> you can stub them out with the "moduleNameMapper" config option.
> 
> You'll find more details and examples of these config options in the docs:
> https://jestjs.io/docs/configuration
> For information about custom transformations, see:
> https://jestjs.io/docs/code-transformation
> 
> Details:
> 
> /usr/share/nodejs/xdg-basedir/index.js:1
> 
> ({"Object.":function(module,exports,require,__dirname,__filename,jest){import
>  os from 'os';
>   
> ^^
> 
> SyntaxError: Cannot use import statement outside a module
> 
>   1372 | try {
>   1373 |   const scriptFilename = 
> this._resolver.isCoreModule(filename) ? `jest-nodejs-core-${filename}` : 
> filename;
> > 1374 |   return new 
> (_vm().Script)(this.wrapCodeInModuleWrapper(scriptSource), {
>|  ^
>   1375 | displayErrors: true,
>   1376 | filename: scriptFilename,
>   1377 | // @ts-expect-error: Experimental ESM API
> 
>   at Runtime.createScriptFromCode 
> (../../../usr/share/nodejs/jest-runtime/build/index.js:1374:14)
>   at Object. (index.js:4:1)
> 
> Test Suites: 1 failed, 1 total
> Tests:   0 total
> Snapshots:   0 total
> Time:1.483 s
> Ran all test suites matching /test.js/i.
> 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-configstore_6.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.

Bug#1009574: node-transformers: FTBFS: TypeError: Cannot read property 'indexOf' of null

[Lucas Nussbaum]

Source: node-transformers
Version: 3.1.0+~1.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
> Link node_modules/jstransformer -> ../jstransformer
>dh_auto_build --buildsystem=nodejs
> No build command found, searching known files
> No build command found, searching known files
>dh_auto_test --buildsystem=nodejs
>   ln -s ../debian/tests/test_modules/is-browser node_modules/is-browser
>   ln -s ../debian/tests/test_modules/test-result node_modules/test-result
>   ln -s ../debian/tests/test_modules/testit node_modules/testit
>   ln -s ../debian/tests/test_modules/wtfnode node_modules/wtfnode
>   ln -s ../. node_modules/transformers
>   cd ./jstransformer && sh -ex ../debian/nodejs/jstransformer/test
> + node test
> /<>/debian/tests/test_modules/wtfnode/index.js:62
> stack[i].file.indexOf(path.sep) !== -1 &&
>   ^
> 
> TypeError: Cannot read property 'indexOf' of null
> at findCallsite 
> (/<>/debian/tests/test_modules/wtfnode/index.js:62:31)
> at Socket.EventEmitter.init 
> (/<>/debian/tests/test_modules/wtfnode/index.js:175:28)
> at Socket.EventEmitter (events.js:88:21)
> at Socket.Stream (internal/streams/legacy.js:11:6)
> at Socket.Readable (internal/streams/readable.js:188:10)
> at Socket.Duplex (internal/streams/duplex.js:56:12)
> at new Socket (net.js:315:17)
> at createWritableStdioStream 
> (internal/bootstrap/switches/is_main_thread.js:72:18)
> at process.getStdout [as stdout] 
> (internal/bootstrap/switches/is_main_thread.js:122:12)
> at get ()
> dh_auto_test: error: cd ./jstransformer && sh -ex 
> ../debian/nodejs/jstransformer/test returned exit code 1


The full build log is available from:
http://qa-logs.debian.net/2022/04/12/node-transformers_3.1.0+~1.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.

Bug#1009573: node-performance-now: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 77

[Lucas Nussbaum]

Source: node-performance-now
Version: 2.1.0+debian-3
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):
> make[1]: Entering directory '/<>'
> coffee --compile -m --output lib/ src/
> make[1]: Leaving directory '/<>'
>dh_auto_test --buildsystem=nodejs
>   mkdir -p node_modules
>   ln -s ../debian/tests/test_modules/call-delayed 
> node_modules/call-delayed
>   ln -s ../debian/tests/test_modules/chai-increasing 
> node_modules/chai-increasing
>   ln -s ../. node_modules/performance-now
>   /bin/sh -ex debian/tests/pkg-js/test
> + mocha --require coffee-script/register test/performance-now.coffee 
> test/scripts.coffee
> (node:2928307) [DEP0005] DeprecationWarning: Buffer() is deprecated due to 
> security and usability issues. Please use the Buffer.alloc(), 
> Buffer.allocUnsafe(), or Buffer.from() methods instead.
> (Use `node --trace-deprecation ...` to show where the warning was created)
> 
> 
>   now
> undefined reported time differs at most 1ms from a freshly reported uptime
> undefined two subsequent calls return an increasing number
> undefined has less than 20 microseconds overhead
> undefined can be called 1 million times in under 1 second (averaging 
> under 1 microsecond per call) (145ms)
> undefined for 10,000 numbers, number n is never bigger than number n-1 
> (80ms)
> undefined shows that at least 0.2 ms has passed after a timeout of 1 ms
> undefined shows that at most 3 ms has passed after a timeout of 1 ms
> undefined shows that at least 190ms ms has passed after a timeout of 
> 200ms (201ms)
> undefined shows that at most 220 ms has passed after a timeout of 200ms 
> (201ms)
> 
>   scripts/initital-value.coffee (module.uptime(), expressed in milliseconds)
> undefined printed 138.579
> undefined printed a value above 80
> undefined printed a value below 350
> 
>   scripts/delayed-require.coffee (sum of uptime and 250 ms delay`)
> undefined printed 588.16
> undefined printed a value above 340
> undefined printed a value below 600
> 
>   scripts/delayed-call.coffee (sum of uptime and 250 ms delay`)
> undefined printed 451.145
> undefined printed a value above 340
> undefined printed a value below 600
> 
>   scripts/difference.coffee
> undefined printed 0.002
> 1) printed a value above 0.002
> undefined printed a value below 0.07
> 
> 
>   20 passing (663ms)
>   1 failing
> 
>   1) scripts/difference.coffee
>printed a value above 0.002:
> 
>   AssertionError: expected 0.002 to be above 0.002
>   + expected - actual
> 
> 
>   at Context. (test/scripts.coffee:26:47)
>   at callFn (/usr/share/nodejs/mocha/lib/runnable.js:366:21)
>   at Test.Runnable.run (/usr/share/nodejs/mocha/lib/runnable.js:354:5)
>   at Runner.runTest (/usr/share/nodejs/mocha/lib/runner.js:678:10)
>   at /usr/share/nodejs/mocha/lib/runner.js:801:12
>   at next (/usr/share/nodejs/mocha/lib/runner.js:593:14)
>   at /usr/share/nodejs/mocha/lib/runner.js:603:7
>   at next (/usr/share/nodejs/mocha/lib/runner.js:486:14)
>   at Immediate._onImmediate (/usr/share/nodejs/mocha/lib/runner.js:571:5)
>   at processImmediate (internal/timers.js:464:21)
>   
> 
> 
> 
> + exit 77
> dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 
> 77


The full build log is available from:
http://qa-logs.debian.net/2022/04/12/node-performance-now_2.1.0+debian-3_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.

Bug#1009572: node-cache-loader: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1

[Lucas Nussbaum]

Source: node-cache-loader
Version: 4.1.0+~cs2.0.0-2
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):
> make[1]: Entering directory '/<>'
> babeljs-7 src -d dist --ignore 'src/**/*.test.js' --copy-files
> Successfully compiled 2 files with Babel (485ms).
> make[1]: Leaving directory '/<>'
>dh_auto_test --buildsystem=nodejs
>   ln -s ../. node_modules/cache-loader
>   /bin/sh -ex debian/tests/pkg-js/test
> + cp test/__snapshots__/validate-options.test.js.snap 
> test/__snapshots__/validate-options.test.js.save
> + jest -u --ci test/cjs.test.js test/validate-options.test.js
> jest-haste-map: Haste module naming collision: cache-loader
>   The following files share their name; please adjust your hasteImpl:
> * /package.json
> * /.pc/fix-for-mkdirp.diff/package.json
> 
> FAIL test/cjs.test.js
>   ● Test suite failed to run
> 
> TypeError: findUp.sync is not a function
> 
>   11 |
>   12 | module.exports.sync = cwd => {
> > 13 |const filePath = findUp.sync('package.json', {cwd});
>  |^
>   14 |return filePath && path.dirname(filePath);
>   15 | };
>   16 |
> 
>   at AsyncFunction.sync (../../../usr/share/nodejs/pkg-dir/index.js:13:26)
>   at findCacheDir 
> (../../../usr/share/nodejs/find-cache-dir/index.js:55:21)
>   at Object. (src/index.js:24:19)
>   at Object. (test/cjs.test.js:1:1)
> 
> FAIL test/validate-options.test.js
>   ● Test suite failed to run
> 
> TypeError: findUp.sync is not a function
> 
>   11 |
>   12 | module.exports.sync = cwd => {
> > 13 |const filePath = findUp.sync('package.json', {cwd});
>  |^
>   14 |return filePath && path.dirname(filePath);
>   15 | };
>   16 |
> 
>   at AsyncFunction.sync (../../../usr/share/nodejs/pkg-dir/index.js:13:26)
>   at findCacheDir 
> (../../../usr/share/nodejs/find-cache-dir/index.js:55:21)
>   at Object. (src/index.js:24:19)
>   at Object. (test/validate-options.test.js:1:1)
> 
> Test Suites: 2 failed, 2 total
> Tests:   0 total
> Snapshots:   0 total
> Time:5.057 s
> Ran all test suites matching 
> /test\/cjs.test.js|test\/validate-options.test.js/i.
> 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-cache-loader_4.1.0+~cs2.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=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.

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

[Lucas Nussbaum]

Source: node-call-limit
Version: 1.1.1-2
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/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=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.

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

[Lucas Nussbaum]

Source: node-dashdash
Version: 2.0.0-2
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/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
&g

Bug#1009569: node-stack-utils: FTBFS: ERROR: Coverage for statements (84.61%) does not meet global threshold (100%)

[Lucas Nussbaum]

Source: node-stack-utils
Version: 2.0.5+~2.0.1-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
> Link node_modules/@types/stack-utils -> ../../types-stack-utils
>dh_auto_build --buildsystem=nodejs
> No build command found, searching known files
> No build command found, searching known files
>dh_auto_test --buildsystem=nodejs
>   ln -s ../. node_modules/stack-utils
>   /bin/sh -ex debian/tests/pkg-js/test
> + + ls test/_utils.js test/at.js test/internals.js test/long-stack-traces.js 
> test/node-modules.js test/parse-line-fixtures.js test/test.js
> + grepgrep -v test/long-stack-traces.js
>  -v test/test.js
> + tap -J test/_utils.js test/at.js test/internals.js test/node-modules.js 
> test/parse-line-fixtures.js
> TAP version 13
> ok 1 - test/_utils.js # time=6.611ms {
> ok 1 - this is fine
> 1..1
> # time=6.611ms
> }
> 
> ok 2 - test/at.js # time=14.43ms {
> ok 1 - should match pattern provided
> ok 2 - should match pattern provided
> 1..2
> # time=14.43ms
> }
> 
> ok 3 - test/internals.js # time=25.792ms {
> # Subtest: removes namespaced internal modules
> 1..1
> ok 1 - should be equal
> ok 1 - removes namespaced internal modules # time=15.488ms
> 
> 1..1
> # time=25.792ms
> }
> 
> ok 4 - test/node-modules.js # time=11.841ms {
> ok 1 - should match pattern provided
> ok 2 - should not match pattern provided
> ok 3 - should match pattern provided
> ok 4 - should not match pattern provided
> ok 5 - should match pattern provided
> ok 6 - should not match pattern provided
> ok 7 - should match pattern provided
> ok 8 - should not match pattern provided
> ok 9 - should match pattern provided
> ok 10 - should not match pattern provided
> ok 11 - should match pattern provided
> ok 12 - should not match pattern provided
> 1..12
> # time=11.841ms
> }
> 
> ok 5 - test/parse-line-fixtures.js # time=61.8ms {
> 1..74
> ok 1 - "at Object.[foo] (__dirname/generate-parse-fixture.js:420:69)"
> ok 2 - "Object.[foo] (__dirname/generate-parse-fixture.js:420:69)"
> ok 3 - "at Object. 
> (__dirname/generate-parse-fixture.js:420:69)"
> ok 4 - "Object. (__dirname/generate-parse-fixture.js:420:69)"
> ok 5 - "at Module._compile (module.js:571:32)"
> ok 6 - "Module._compile (module.js:571:32)"
> ok 7 - "at Object.Module._extensions..js (module.js:580:10)"
> ok 8 - "Object.Module._extensions..js (module.js:580:10)"
> ok 9 - "at Module.load (module.js:488:32)"
> ok 10 - "Module.load (module.js:488:32)"
> ok 11 - "at tryModuleLoad (module.js:447:12)"
> ok 12 - "tryModuleLoad (module.js:447:12)"
> ok 13 - "at Function.Module._load (module.js:439:3)"
> ok 14 - "Function.Module._load (module.js:439:3)"
> ok 15 - "at Module.runMain (module.js:605:10)"
> ok 16 - "Module.runMain (module.js:605:10)"
> ok 17 - "at run (bootstrap_node.js:418:7)"
> ok 18 - "run (bootstrap_node.js:418:7)"
> ok 19 - "at startup (bootstrap_node.js:139:9)"
> ok 20 - "startup (bootstrap_node.js:139:9)"
> ok 21 - "at Object.asdf ][)( 
> \\u\\u0001\\u0002\\u0003\\u001b[44;37m foo 
> (__dirname/generate-parse-fixture.js:420:69)"
> ok 22 - "Object.asdf ][)( \\u\\u0001\\u0002\\u0003\\u001b[44;37m foo 
> (__dirname/generate-parse-fixture.js:420:69)"
> ok 23 - "at Object.asdf (__dirname/generate-parse-fixture.js:420:69) 
> (__dirname/generate-parse-fixture.js:420:69)"
> ok 24 - "Object.asdf (__dirname/generate-parse-fixture.js:420:69) 
> (__dirname/generate-parse-fixture.js:420:69)"
> ok 25 - "at Object.eval (__dirname/generate-parse-fixture.js:420:69)"
> ok 26 - "Object.eval (__dirname/generate-parse-fixture.js:420:69)"
> ok 27 - "at eval (eval at  
> (__dirname/generate-parse-fixture.js:420:69), :1:5)"
> ok 28 - "eval (eval at  
> (__dirname/generate-parse-fixture.js:420:69), :1:5)"
> ok 29 - "at Object.a (s) d [f] 
> (__dirname/generate-parse-fixture.js:420

Bug#1009568: node-proper-lockfile: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1

[Lucas Nussbaum]

Source: node-proper-lockfile
Version: 4.1.2-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/\@segment
>   ln -s ../../debian/tests/test_modules/\@segment/clear-timeouts 
> node_modules/\@segment/clear-timeouts
>   ln -s ../debian/tests/test_modules/delay node_modules/delay
>   ln -s ../debian/tests/test_modules/p-defer node_modules/p-defer
>   ln -s ../debian/tests/test_modules/stable node_modules/stable
>   ln -s ../debian/tests/test_modules/thread-sleep 
> node_modules/thread-sleep
>   ln -s ../. node_modules/proper-lockfile
>   /bin/sh -ex debian/tests/pkg-js/test
> + jest --env node --ci -i
> FAIL test/lock.test.js
>   ● Test suite failed to run
> 
> Jest encountered an unexpected token
> 
> Jest failed to parse a file. This happens e.g. when your code or its 
> dependencies use non-standard JavaScript syntax, or when Jest is not 
> configured to support such syntax.
> 
> Out of the box Jest supports Babel, which will be used to transform your 
> files into valid JS based on your Babel configuration.
> 
> By default "node_modules" folder is ignored by transformers.
> 
> Here's what you can do:
>  • If you are trying to use ECMAScript Modules, see 
> https://jestjs.io/docs/ecmascript-modules for how to enable it.
>  • If you are trying to use TypeScript, see 
> https://jestjs.io/docs/getting-started#using-typescript
>  • To have some of your "node_modules" files transformed, you can specify 
> a custom "transformIgnorePatterns" in your config.
>  • If you need a custom transformation specify a "transform" option in 
> your config.
>  • If you simply want to mock your non-JS modules (e.g. binary assets) 
> you can stub them out with the "moduleNameMapper" config option.
> 
> You'll find more details and examples of these config options in the docs:
> https://jestjs.io/docs/configuration
> For information about custom transformations, see:
> https://jestjs.io/docs/code-transformation
> 
> Details:
> 
> /usr/share/nodejs/path-key/index.js:1
> 
> ({"Object.":function(module,exports,require,__dirname,__filename,jest){export
>  default function pathKey(options = {}) {
>   
> ^^
> 
> SyntaxError: Unexpected token 'export'
> 
>   1372 | try {
>   1373 |   const scriptFilename = 
> this._resolver.isCoreModule(filename) ? `jest-nodejs-core-${filename}` : 
> filename;
> > 1374 |   return new 
> (_vm().Script)(this.wrapCodeInModuleWrapper(scriptSource), {
>|  ^
>   1375 | displayErrors: true,
>   1376 | filename: scriptFilename,
>   1377 | // @ts-expect-error: Experimental ESM API
> 
>   at Runtime.createScriptFromCode 
> (../../../usr/share/nodejs/jest-runtime/build/index.js:1374:14)
>   at Object. (../../../usr/share/nodejs/execa/execa.cjs:8:17)
> 
> PASS test/unlock.test.js (14.822 s)
> PASS test/check.test.js
> PASS test/sync.test.js
> FAIL test/misc.test.js
>   ● Test suite failed to run
> 
> Jest encountered an unexpected token
> 
> Jest failed to parse a file. This happens e.g. when your code or its 
> dependencies use non-standard JavaScript syntax, or when Jest is not 
> configured to support such syntax.
> 
> Out of the box Jest supports Babel, which will be used to transform your 
> files into valid JS based on your Babel configuration.
> 
> By default "node_modules" folder is ignored by transformers.
> 
> Here's what you can do:
>  • If you are trying to use ECMAScript Modules, see 
> https://jestjs.io/docs/ecmascript-modules for how to enable it.
>  • If you are trying to use TypeScript, see 
> https://jestjs.io/docs/getting-started#using-typescript
>  • To have some of your "node_modules" files transformed, you can specify 
> a custom "transformIgnorePatterns" in your config.
>  • If you need a custom transformation specify a "transform" option in 
> your config.
>  • If you simply w

Bug#1009567: node-aproba: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1

[Lucas Nussbaum]

Source: node-aproba
Version: 2.0.0-2
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/aproba
>   /bin/sh -ex debian/tests/pkg-js/test
> + tap test/aproba-arg-validation.js test/index.js
> TAP version 13
> (node:1721090) DeprecationWarning: is() is deprecated, use equal() instead
> (Use `node --trace-deprecation ...` to show where the warning was created)
> not ok 1 - test/aproba-arg-validation.js # time=36.537ms
>   ---
>   env: {}
>   file: test/aproba-arg-validation.js
>   timeout: 3
>   command: /usr/bin/node
>   args:
> - test/aproba-arg-validation.js
>   stdio:
> - 0
> - pipe
> - 2
>   cwd: /<>
>   exitCode: 1
>   ...
> {
> # Subtest: aproba arg validation
> # Missing required argument #1
> ok 1 - missing first arg is error
> # Missing required argument #2
> ok 2 - missing second arg is error
> # Unknown type ¶ in argument #1
> ok 3 - invalid type string
> # Only one error type per argument signature is allowed, more than 
> one found in "OEOEO"
> ok 4 - more than one error arg is error
> # Expected SA arguments but got 3
> ok 5 - too many arguments
> # Expected SA arguments but got 1
> ok 6 - too few arguments
> # Argument #1: Expected string but got array
> ok 7 - first arg not string
> # Argument #2: Expected array but got number
> ok 8 - second arg not arrayish
> not ok 9 - t.done is not a function
>   ---
>   stack: |
> Test. (test/aproba-arg-validation.js:43:5)
> Test.cb (/usr/share/nodejs/libtap/lib/test.js:127:40)
> /usr/share/nodejs/libtap/lib/test.js:369:21
> Test.main (/usr/share/nodejs/libtap/lib/test.js:376:7)
> Test.runMain (/usr/share/nodejs/libtap/lib/base.js:178:15)
> /usr/share/nodejs/libtap/lib/test.js:485:13
> TAP.writeSubComment (/usr/share/nodejs/libtap/lib/test.js:556:5)
> Test. (/usr/share/nodejs/libtap/lib/test.js:484:14)
>   at:
> line: 43
> column: 5
> file: test/aproba-arg-validation.js
> function: Test.
>   type: TypeError
>   tapCaught: testFunctionThrow
>   test: aproba arg validation
>   source: |2
>   })
>   t.done()
> ^
> })
>   ...
> 
> 1..9
> # failed 1 of 9 tests
> not ok 1 - aproba arg validation # time=29.715ms
> 
> 1..1
> (node:1721089) DeprecationWarning: is() is deprecated, use equal() instead
> (Use `node --trace-deprecation ...` to show where the warning was created)
> # failed 1 test
> # time=36.537ms
> }
> 
> not ok 2 - test/index.js # time=47.482ms
>   ---
>   env: {}
>   file: test/index.js
>   timeout: 3
>   command: /usr/bin/node
>   args:
> - test/index.js
>   stdio:
> - 0
> - pipe
> - 2
>   cwd: /<>
>   exitCode: 1
>   ...
> {
> # Subtest: user arg validation
> ok 1 - A matches A
> # Argument #1: Expected array but got string
> ok 2 - A does not match S
> # Argument #1: Expected array but got number
> ok 3 - A does not match N
> # Argument #1: Expected array but got function
> ok 4 - A does not match F
> # Argument #1: Expected array but got object
> ok 5 - A does not match O
> # Argument #1: Expected array but got boolean
> ok 6 - A does not match B
> # Argument #1: Expected array but got error
> ok 7 - A does not match E
> # Argument #1: Expected array but got null
> ok 8 - null throws for A
> # Argument #1: Expected string but got array
> ok 9 - S does not match A
> ok 10 - S matches S
> # Argument #1: Expected string but got number
> ok 11 - S does not match N
> # Argument #1: Expected string but got function
> ok 12 - S does not match F
> # Argument #1: Expected string but got object
&g

Bug#1009566: node-findit2: FTBFS: ERROR: Coverage for statements (87.2%) does not meet global threshold (100%)

[Lucas Nussbaum]

Source: node-findit2
Version: 2.2.3-7
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/findit2
>   /bin/sh -ex debian/tests/pkg-js/test
> + tap test/empty.js test/err.js test/foo.js test/module.js test/stop.js 
> test/symlinks.js
> TAP version 13
> (node:490870) DeprecationWarning: deepEqual() is deprecated, use same() 
> instead
> (Use `node --trace-deprecation ...` to show where the warning was created)
> (node:490869) DeprecationWarning: deepEqual() is deprecated, use same() 
> instead
> (Use `node --trace-deprecation ...` to show where the warning was created)
> ok 1 - test/empty.js # time=28.539ms {
> # Subtest: empty
> 1..1
> ok 1 - should be equivalent
> ok 1 - empty # time=16.557ms
> 
> 1..1
> # time=28.539ms
> }
> 
> ok 2 - test/err.js # time=21.458ms {
> # Subtest: error
> 1..1
> ok 1 - should be equal
> ok 1 - error # time=12.029ms
> 
> 1..1
> # time=21.458ms
> }
> 
> ok 3 - test/foo.js # time=45.581ms {
> # Subtest: foo
> ok 1 - should be equal
> ok 2 - should be equal
> ok 3 - expect truthy value
> ok 4 - should be equal
> ok 5 - expect truthy value
> ok 6 - should be equal
> ok 7 - expect truthy value
> ok 8 - should be equal
> ok 9 - expect truthy value
> ok 10 - should be equal
> ok 11 - expect truthy value
> ok 12 - should be equal
> ok 13 - expect truthy value
> ok 14 - should be equal
> ok 15 - expect truthy value
> ok 16 - should be equal
> ok 17 - expect truthy value
> ok 18 - should be equivalent
> ok 19 - should be equivalent
> ok 20 - should be equivalent
> 1..20
> ok 1 - foo # time=35.869ms
> 
> 1..1
> # time=45.581ms
> }
> 
> (node:490871) DeprecationWarning: deepEqual() is deprecated, use same() 
> instead
> (Use `node --trace-deprecation ...` to show where the warning was created)
> ok 4 - test/module.js # time=16.895ms {
> # Subtest: single file
> 1..2
> ok 1 - should be equal
> ok 2 - should be equivalent
> ok 1 - single file # time=10.239ms
> 
> 1..1
> # time=16.895ms
> }
> 
> ok 5 - test/stop.js # time=13.908ms {
> # Subtest: stop
> 1..1
> ok 1 - should be equal
> ok 1 - stop # time=8.44ms
> 
> 1..1
> # time=13.908ms
> }
> 
> (node:490889) DeprecationWarning: deepEqual() is deprecated, use same() 
> instead
> (Use `node --trace-deprecation ...` to show where the warning was created)
> ok 6 - test/symlinks.js # time=39.561ms {
> # Subtest: links
> ok 1 - expect truthy value
> ok 2 - expect truthy value
> ok 3 - expect truthy value
> ok 4 - expect truthy value
> ok 5 - expect truthy value
> ok 6 - should be equivalent
> ok 7 - should be equivalent
> ok 8 - should be equivalent
> ok 9 - should be equivalent
> 1..9
> ok 1 - links # time=17.415ms
> 
> # Subtest: follow links
> ok 1 - expect truthy value
> ok 2 - expect truthy value
> ok 3 - expect truthy value
> ok 4 - expect truthy value
> ok 5 - expect truthy value
> ok 6 - expect truthy value
> ok 7 - expect truthy value
> ok 8 - expect truthy value
> ok 9 - expect truthy value
> ok 10 - should be equal
> ok 11 - should be equal
> ok 12 - should be equal
> ok 13 - should be equivalent
> ok 14 - should be equivalent
> ok 15 - should be equivalent
> 1..15
> ok 2 - follow links # time=8.892ms
> 
> # Subtest: parent links
> ok 1 - expect truthy value
> ok 2 - expect truthy value
> ok 3 - expect truthy value
> ok 4 - expect truthy value
> ok 5 - expect truthy value
> ok 6 - expect truthy value
> ok 7 - expect truthy value
> ok 8 - expect truthy value
> ok 9 - expect truthy val

Bug#1009565: node-module-deps: FTBFS: ERROR: Coverage for statements (86.71%) does not meet global threshold (100%)

[Lucas Nussbaum]

Source: node-module-deps
Version: 6.2.3-2
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):
> make[1]: Entering directory '/<>'
> help2man --no-info ./bin/cmd.js >debian/module-deps.1
> make[1]: Leaving directory '/<>'
>dh_auto_test --buildsystem=nodejs
>   mkdir -p node_modules
>   ln -s ../. node_modules/module-deps
>   /bin/sh -ex debian/tests/pkg-js/test
> + tap -R spec test/bundle.js test/cache.js test/cache_expose.js 
> test/cache_partial.js test/cache_partial_expose.js test/cache_persistent.js 
> test/cycle.js test/deps.js test/detect.js test/dotdot.js test/expose.js 
> test/file_cache.js test/filter.js test/ignore_missing.js 
> test/ignore_missing_cache.js test/invalid_pkg.js test/noparse.js 
> test/noparse_row.js test/pkg.js test/pkg_filter.js test/quotes.js 
> test/resolve.js test/row_expose.js test/row_expose_name_is_file_transform.js 
> test/row_expose_transform.js test/source.js test/syntax.js 
> test/tr_2dep_module.js test/tr_deps.js test/tr_err.js test/tr_flags.js 
> test/tr_fn.js test/tr_global.js test/tr_module.js test/tr_no_entry.js 
> test/tr_opts.js test/tr_rel.js test/tr_sh.js test/tr_whole_package.js 
> test/tr_write.js test/undef_file.js test/unicode.js
> 
> (node:1666788) DeprecationWarning: equals() is deprecated, use equal() instead
> (Use `node --trace-deprecation ...` to show where the warning was created)
> test/bundle.js
>   bundle
> 
> ✓ should be equal
> 
> test/cache.js
>   uses cache
> 
> ✓ should be equivalent
> 
> test/cache_expose.js
>   cache preserves expose and entry
> 
> ✓ should be equivalent
> 
> test/cache_partial.js
>   uses cache and reads from disk
> 
> ✓ should be equivalent
> 
> test/cache_partial_expose.js
>   preserves expose and entry with partial cache
> 
> ✓ should be equivalent
> 
> test/cache_persistent.js
>   uses persistent cache
> 
> ✓ should be equivalent
> 
>   passes persistent cache error through
> 
> ✓ should be equal
> 
>   allow passing of the raw source as string
> 
> ✓ should be equivalent
> 
>   send file event with persistent cache
> 
> ✓ should be equivalent
> 
> ✓ should be equivalent
> 
>   errors of transforms occur in the correct order with a persistent cache
> 
> ✓ should be equivalent
> 
> ✓ should be equivalent
> 
> ✓ should be equivalent
> 
> test/cycle.js
>   cycle
> 
> ✓ should be equal
> 
> test/deps.js
>   deps
> 
> ✓ should be equivalent
> 
> (node:1666861) DeprecationWarning: deepEqual() is deprecated, use same() 
> instead
> (Use `node --trace-deprecation ...` to show where the warning was created)
> test/detect.js
>   detect
> 
> ✓ should be equal
> 
> test/dotdot.js
>   dotdot
> 
> ✓ should be equivalent
> 
> ✓ should be equivalent
> 
> test/expose.js
>   single id export
> 
> ✓ should be equivalent
> 
> test/file_cache.js
>   uses file cache
> 
> ✓ should be equivalent
> 
> (node:1666888) DeprecationWarning: deepEqual() is deprecated, use same() 
> instead
> (Use `node --trace-deprecation ...` to show where the warning was created)
> test/filter.js
>   can filter core deps
> 
> ✓ should be equal
> 
> ✓ should be equivalent
> 
> ✓ should be equal
> 
> ✓ should be equal
> 
> test/ignore_missing.js
>   ignoreMissing
> 
> ✓ should be equivalent
> 
>   ignoreMissing off
> 
> ✓ should match pattern provided
> 
> test/ignore_missing_cache.js
>   ignoreMissing with cache
> 
> ✓ should be equivalent
> 
> test/invalid_pkg.js
> 
>   ✓ invalid pkg (61.269ms)
> (node:1666935) DeprecationWarning: deepEqual() is deprecated, use same() 
> instead
> (Use `node --trace-deprecation ...` to show where the warning was created)
> test/noparse.js
>   noParse
> 
> ✓ should be equivalent
> 
> (node:1666950) DeprecationWarning: deepEqual() is deprecated, use same() 
> instead
> (Use `node --trace-deprecation ...` to show where the warning was created)
> test/noparse_row.js
>   noParse row
> 
> ✓ should be equivalent
> 
> (node:1666964) DeprecationWarning: deepEqual() is deprecated, use same() 
> instead
> (Use `node --trace-deprecation ...` to show where the warning was created)
> test/pkg.js
>   pkg
> 
> ✓ should be equivalent
> 
> ✓ should be equivalent
> 
> ✓ should be equivalent

Bug#1009564: node-stream-splicer: FTBFS: ERROR: Coverage for statements (92.36%) does not meet global threshold (100%)

[Lucas Nussbaum]

Source: node-stream-splicer
Version: 2.0.1-2
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-splicer
>   /bin/sh -ex debian/tests/pkg-js/test
> + tap -R spec test/combiner.js test/combiner_stream.js test/empty.js 
> test/empty_no_data.js test/get.js test/multipush.js test/multiunshift.js 
> test/nested.js test/nested_middle.js test/pop.js test/push.js test/shift.js 
> test/splice.js test/unshift.js
> 
> test/combiner.js
> 
>   ✓ should be deeply equivalent
> test/combiner_stream.js
> 
>   ✓ should be deeply equivalent
> test/empty.js
> 
>   ✓ should be deeply equivalent
> test/empty_no_data.js
> 
>   ✓ should be deeply equivalent
> test/get.js
> 
>   ✓ 0
> 
>   ✓ 1
> 
>   ✓ 2
> 
>   ✓ 3
> 
>   ✓ 4
> 
>   ✓ 5
> 
>   ✓ -1
> 
>   ✓ -1
> 
>   ✓ -2
> 
>   ✓ -3
> 
>   ✓ -4
> 
>   ✓ -5
> 
>   ✓ should be strictly equal
> 
>   ✓ should be strictly equal
> 
>   ✓ should be strictly equal
> 
>   ✓ should be strictly equal
> test/multipush.js
> 
>   ✓ should be deeply equivalent
> test/multiunshift.js
> 
>   ✓ should be deeply equivalent
> test/nested.js
> 
>   ✓ should be deeply equivalent
> test/nested_middle.js
> 
>   ✓ should be deeply equivalent
> test/pop.js
> 
>   ✓ should be strictly equal
> 
>   ✓ should be strictly equal
> 
>   ✓ should be deeply equivalent
> test/push.js
> 
>   ✓ should be strictly equal
> 
>   ✓ should be deeply equivalent
> 
>   ✓ should be deeply equivalent
> 
>   ✓ should be deeply equivalent
> 
>   ✓ should be deeply equivalent
> 
>   ✓ should be deeply equivalent
> 
>   ✓ should be deeply equivalent
> 
>   ✓ should be strictly equal
> 
>   ✓ should be strictly equal
> 
>   ✓ should be deeply equivalent
> 
>   ✓ should be deeply equivalent
> 
>   ✓ should be deeply equivalent
> 
>   ✓ should be deeply equivalent
> 
>   ✓ should be deeply equivalent
> 
>   ✓ should be deeply equivalent
> test/shift.js
> 
>   ✓ a
> 
>   ✓ b
> 
>   ✓ c
> 
>   ✓ a
> 
>   ✓ b
> 
>   ✓ c
> 
>   ✓ b
> 
>   ✓ c
> 
>   ✓ b
> 
>   ✓ c
> 
>   ✓ should be strictly equal
> 
>   ✓ should be strictly equal
> 
>   ✓ should be strictly equal
> 
>   ✓ should be strictly equal
> test/splice.js
> 
>   ✓ d
> 
>   ✓ should be strictly equal
> 
>   ✓ d
> 
>   ✓ should be strictly equal
> 
>   ✓ thousander
> 
>   ✓ should be strictly equal
> 
>   ✓ thousander
> 
>   ✓ should be strictly equal
> 
>   ✓ should be deeply equivalent
> test/unshift.js
> 
>   ✓ b
> 
>   ✓ c
> 
>   ✓ b
> 
>   ✓ c
> 
>   ✓ a
> 
>   ✓ b
> 
>   ✓ c
> 
>   ✓ a
> 
>   ✓ b
> 
>   ✓ c
> 
>   ✓ should be strictly equal
> 
>   ✓ should be strictly equal
> 
>   ✓ should be strictly equal
> 
>   ✓ should be strictly equal
> 
>   79 passing (2s)
> ERROR: Coverage for lines (94.48%) does not meet global threshold (100%)
> ERROR: Coverage for functions (85%) does not meet global threshold (100%)
> ERROR: Coverage for branches (83.87%) does not meet global threshold (100%)
> ERROR: Coverage for statements (92.36%) does not meet global threshold (100%)
> --|-|--|-|-|--
> File  | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s
> --|-|--|-|-----|--
> All files |   92.36 |83.87 |  85 |   94.48 |  
>  index.js |   92.36 |    83.87 |  85 |   94.48 | 15-16,94,129-130,183,191 
> --|-|--|-|-|--
> 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-splicer_2.0.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=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.

Bug#1009563: node-mkdirp: FTBFS: ERROR: Coverage for statements (83.92%) does not meet global threshold (100%)

[Lucas Nussbaum]

Source: node-mkdirp
Version: 1.0.4+~1.0.2-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
> Link node_modules/@types/mkdirp -> ../../types-mkdirp
>dh_auto_build --buildsystem=nodejs
> No build command found, searching known files
> No build command found, searching known files
>dh_auto_test --buildsystem=nodejs
>   ln -s ../. node_modules/mkdirp
>   /bin/sh -ex debian/tests/pkg-js/test
> + ls test/cmd.js test/find-made.js test/index.js test/mkdirp-manual.js+  
> test/mkdirp-native.js test/opts-arg.jsgrep -v test/cmd
> + grep -v test/find-made
>  test/path-arg.js test/use-native.js
> + grep -v test/index
> + tap test/mkdirp-manual.js test/mkdirp-native.js test/opts-arg.js 
> test/path-arg.js test/use-native.js
> TAP version 13
> ok 1 - test/mkdirp-manual.js # time=45.264ms {
> # Subtest: mkdirpManual / just calls implementation
> # Subtest: success is fine, of course
> ok 1 - should be equal
> ok 2 - should be equal
> ok 3 - should be equal
> ok 4 - should be equal
> 1..4
> ok 1 - success is fine, of course # time=11.718ms
> 
> # Subtest: EISDIR is expected and ignored
> ok 1 - should be equal
> ok 2 - should be equal
> ok 3 - should be equal
> ok 4 - should be equal
> 1..4
> ok 2 - EISDIR is expected and ignored # time=2.049ms
> 
> # Subtest: other failures are failures
> ok 1 - expected to throw
> ok 2 - expect rejected Promise
> 1..2
> ok 3 - other failures are failures # time=6.534ms
> 
> 1..3
> ok 1 - mkdirpManual / just calls implementation # time=33.378ms
> 
> # Subtest: unknown failure types are failures
> ok 1 - expected to throw
> ok 2 - expect rejected Promise
> 1..2
> ok 2 - unknown failure types are failures # time=1.812ms
> 
> 1..2
> # time=45.264ms
> }
> 
> ok 2 - test/mkdirp-native.js # time=25.452ms {
> # Subtest: mkdirpNative / just calls implementation
> ok 1 - should be equal
> ok 2 - should be equal
> ok 3 - should be equal
> ok 4 - should be equal
> 1..4
> ok 1 - mkdirpNative / just calls implementation # time=7.155ms
> 
> # Subtest: other errors are raised to caller
> ok 1 - expected to throw
> ok 2 - expect rejected Promise
> 1..2
> ok 2 - other errors are raised to caller # time=10.198ms
> 
> 1..2
> # time=25.452ms
> }
> 
> ok 3 - test/opts-arg.js # time=37.199ms {
> ok 1 - null
> ok 2 - false
> ok 3 - undefined
> ok 4 - empty object
> ok 5 - numeric mode
> ok 6 - string mode
> ok 7 - empty custom fs
> ok 8 - custom stat/statSync
> ok 9 - custom fs with stat/statSync
> ok 10 - expected to throw: TypeError invalid options argument
> 1..10
> # time=37.199ms
> }
> 
> ok 4 - test/path-arg.js # time=799.022ms {
> # Subtest: node ./test/path-arg.js
> ok 1 - should be equal
> ok 2 - expected to throw: Error path must be a string without null 
> bytes
> ok 3 - expected to throw: Error Illegal characters in path
> ok 4 - expected to throw: Error Illegal characters in path
> ok 5 - expected to throw: Error Illegal characters in path
> ok 6 - expected to throw: Error Illegal characters in path
> ok 7 - expected to throw: Error Illegal characters in path
> ok 8 - expected to throw: Error Illegal characters in path
> ok 9 - expected to throw: Error Illegal characters in path
> 1..9
> # time=21.664ms
> ok 1 - node ./test/path-arg.js # time=21.664ms
> 
> ok 2 - should be equal
> ok 3 - expected to throw: Error path must be a string without null bytes
> 1..3
> # time=799.022ms
> }
> 
> ok 5 - test/use-native.js # time=630.964ms {
> # Subtest: node ./test/use-native.js
> ok 1 - should be equal
> ok 2 - should be equal
> ok 3 - should be equal
> ok 4 - should be equal
> 1..4
> # time=8.048ms
> ok 1 - node ./test/use-native.js # time=8.048ms
> 
> # Subtest: node ./test/use-native.js
>   

Bug#1009562: node-fs.realpath: FTBFS: ERROR: Coverage for statements (21.46%) does not meet global threshold (100%)

[Lucas Nussbaum]

Source: node-fs.realpath
Version: 1.0.0-2
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/fs.realpath
>   /bin/sh -ex debian/tests/pkg-js/test
> + tap test/monkeypatching.js test/symlinks.js
> TAP version 13
> (node:1007448) DeprecationWarning: notEqual() is deprecated, use not() instead
> (Use `node --trace-deprecation ...` to show where the warning was created)
> ok 1 - test/monkeypatching.js # time=10.619ms {
> ok 1 - should be equal
> ok 2 - should be equal
> ok 3 - should not be equal
> ok 4 - should not be equal
> 1..4
> # time=10.619ms
> }
> 
> ok 2 - test/symlinks.js # time=99.428ms {
> # Subtest: setup
> 1..0
> ok 1 - setup # time=3.463ms
> 
> # Subtest: symlinks = 1
> 1..2
> ok 1 - should be equal
> ok 2 - should be equal
> ok 2 - symlinks = 1 # time=13.808ms
> 
> # Subtest: symlinks = 128
> 1..2
> ok 1 - should be equal
> ok 2 - should be equal
> ok 3 - symlinks = 128 # time=20.866ms
> 
> # Subtest: symlinks = 256
> 1..2
> ok 1 - should be equal
> ok 2 - should be equal
> ok 4 - symlinks = 256 # time=51.85ms
> 
> # Subtest: cleanup
> 1..0
> ok 5 - cleanup # time=0.615ms
> 
> 1..5
> # time=99.428ms
> }
> 
> 1..2
> # time=955.542ms
> ERROR: Coverage for lines (23.03%) does not meet global threshold (100%)
> ERROR: Coverage for functions (28.57%) does not meet global threshold (100%)
> ERROR: Coverage for branches (7.07%) does not meet global threshold (100%)
> ERROR: Coverage for statements (21.46%) does not meet global threshold (100%)
> --|-|--|-|-|
> File  | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s
>   
> --|-|--|-|-|
> All files |   21.46 | 7.07 |   28.57 |   23.03 |  
>   
>  index.js |   81.81 |33.33 | 100 |   81.81 | 26,35,44,50-53   
>   
>  old.js   |7.63 | 3.06 |   0 |8.33 | 
> 34-66,74,81,88-179,184-301 
> --|-|--|-|-|
> 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-fs.realpath_1.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=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.

Bug#1009561: node-parse-base64vlq-mappings: FTBFS: ERROR: Coverage for statements (79.31%) does not meet global threshold (100%)

[Lucas Nussbaum]

Source: node-parse-base64vlq-mappings
Version: 0.1.4-6
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/parse-base64vlq-mappings
>   /bin/sh -ex debian/tests/pkg-js/test
> + tap test/parse-base64vlq-mappings.js
> TAP version 13
> (node:117004) DeprecationWarning: deepEqual() is deprecated, use same() 
> instead
> (Use `node --trace-deprecation ...` to show where the warning was created)
> ok 1 - test/parse-base64vlq-mappings.js # time=21.206ms {
> # Subtest: parsing generated one to one mappings with last line having no 
> original
> ok 1 - parses out added mappings
> 1..1
> ok 1 - parsing generated one to one mappings with last line having no 
> original # time=11.255ms
> 
> # Subtest: parsing generated offset mappings with last line having no 
> original
> ok 1 - parses out added mappings
> 1..1
> ok 2 - parsing generated offset mappings with last line having no 
> original # time=2.145ms
> 
> 1..2
> # time=21.206ms
> }
> 
> 1..1
> # time=857.86ms
> ERROR: Coverage for lines (79.31%) does not meet global threshold (100%)
> ERROR: Coverage for functions (62.5%) does not meet global threshold (100%)
> ERROR: Coverage for branches (57.14%) does not meet global threshold (100%)
> ERROR: Coverage for statements (79.31%) does not meet global threshold (100%)
> ---|-|--|-|-|---
> File   | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s 
> ---|-|--|-|-|---
> All files  |   79.31 |57.14 |62.5 |   79.31 |   
>  base64-vlq.js |   66.66 |   25 |  50 |   66.66 | 40,63-79,95   
>  base64.js |   69.23 |   25 |   66.66 |   69.23 | 21-24,34  
>  index.js  |   92.68 |81.25 | 100 |   92.68 | 29,47,59  
> ---|-|--|-|-|---
> 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-parse-base64vlq-mappings_0.1.4-6_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.

Bug#1009560: node-mute-stream: FTBFS: ERROR: Coverage for statements (75.36%) does not meet global threshold (100%)

[Lucas Nussbaum]

Source: node-mute-stream
Version: 0.0.8+~0.0.1-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
> Link node_modules/@types/mute-stream -> ../../types-mute-stream
>dh_auto_build --buildsystem=nodejs
> No build command found, searching known files
> No build command found, searching known files
>dh_auto_test --buildsystem=nodejs
>   ln -s ../. node_modules/mute-stream
>   /bin/sh -ex debian/tests/pkg-js/test
> + tap test
> TAP version 13
> ok 1 - test/basic.js # time=25.16ms {
> # Subtest: incoming
> ok 1 - should be equal
> ok 2 - should be equal
> ok 3 - should be equal
> 1..3
> ok 1 - incoming # time=5.356ms
> 
> # Subtest: outgoing
> ok 1 - should be equal
> ok 2 - should be equal
> ok 3 - should be equal
> 1..3
> ok 2 - outgoing # time=1.268ms
> 
> # Subtest: isTTY
> ok 1 - should be equal
> 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
> ok 13 - should be equal
> ok 14 - should be equal
> ok 15 - should be equal
> ok 16 - should be equal
> ok 17 - should be equal
> ok 18 - should be equal
> ok 19 - should be equal
> ok 20 - should be equal
> 1..20
> ok 3 - isTTY # time=2.839ms
> 
> # Subtest: pause/resume incoming
> ok 1 - should be equal
> ok 2 - should be equal
> ok 3 - should be equal
> ok 4 - should be equal
> ok 5 - saw all events
> 1..5
> ok 4 - pause/resume incoming # time=1.175ms
> 
> # Subtest: replace with *
> ok 1 - should be equal
> 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
> 1..9
> ok 5 - replace with * # time=1.679ms
> 
> # Subtest: replace with ~YARG~
> ok 1 - should be equal
> 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
> 1..9
> ok 6 - replace with ~YARG~ # time=1.206ms
> 
> 1..6
> # time=25.16ms
> }
> 
> 1..1
> # time=721.218ms
> ERROR: Coverage for lines (77.77%) does not meet global threshold (100%)
> ERROR: Coverage for functions (93.33%) does not meet global threshold (100%)
> ERROR: Coverage for branches (57.14%) does not meet global threshold (100%)
> ERROR: Coverage for statements (75.36%) does not meet global threshold (100%)
> --|-|--|-|-|-
> File  | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s
>
> --|-|--|-|-|-
> All files |   75.36 |57.14 |   93.33 |   77.77 |  
>
>  mute.js  |   75.36 |57.14 |   93.33 |   77.77 | 
> 104-110,114-116,127,137-140 
> --|-|--|-|-|-
> 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-mute-stream_0.0.8+~0.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=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.

Bug#1009559: node-falafel: FTBFS: ERROR: Coverage for statements (98.11%) does not meet global threshold (100%)

[Lucas Nussbaum]

Source: node-falafel
Version: 2.2.4-3
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/falafel
>   /bin/sh -ex debian/tests/pkg-js/test
> + tap -R spec test/array.js test/async.js test/custom-parser.js test/es6.js 
> test/for.js test/inspect.js test/opts.js test/parent.js
> 
> Since Acorn 8.0.0, options.ecmaVersion is required.
> Defaulting to 2020, but this will stop working in the future.
> Since Acorn 8.0.0, options.ecmaVersion is required.
> Defaulting to 2020, but this will stop working in the future.
> Since Acorn 8.0.0, options.ecmaVersion is required.
> Defaulting to 2020, but this will stop working in the future.
> Since Acorn 8.0.0, options.ecmaVersion is required.
> Defaulting to 2020, but this will stop working in the future.
> Since Acorn 8.0.0, options.ecmaVersion is required.
> Defaulting to 2020, but this will stop working in the future.
> Since Acorn 8.0.0, options.ecmaVersion is required.
> Defaulting to 2020, but this will stop working in the future.
> test/array.js
> 
>   ✓ should be deeply equivalent
> 
>   ✓ should be deeply equivalent
> 
>   ✓ should be deeply equivalent
> 
>   ✓ should be deeply equivalent
> 
>   ✓ should be deeply equivalent
> test/async.js
> 
>   ✓ should be deeply equivalent
> 
>   ✓ should be deeply equivalent
> 
>   ✓ should be deeply equivalent
> 
>   ✓ should be deeply equivalent
> 
>   ✓ should be deeply equivalent
> test/custom-parser.js
> 
>   ✓ should be strictly equal
> 
>   ✓ should be strictly equal
> 
>   ✓ should be strictly equal
> 
>   ✓ should be strictly equal
> 
>   ✓ should be strictly equal
> 
>   ✓ should be strictly equal
> 
>   ✓ should be strictly equal
> 
>   ✓ should be strictly equal
> 
>   ✓ should be strictly equal
> 
>   ✓ should be strictly equal
> 
>   ✓ should be strictly equal
> 
>   ✓ should be strictly equal
> 
>   ✓ should be strictly equal
> 
>   ✓ should be strictly equal
> 
>   ✓ should be strictly equal
> 
>   ✓ should be strictly equal
> 
>   ✓ should be strictly equal
> 
>   ✓ should be strictly equal
> 
>   ✓ should be strictly equal
> 
>   ✓ should be strictly equal
> 
>   ✓ should be strictly equal
> 
>   ✓ should be strictly equal
> 
>   ✓ should be strictly equal
> 
>   ✓ should be strictly equal
> 
>   ✓ should be strictly equal
> test/es6.js
> 
>   ✓ should be strictly equal
> test/for.js
> 
>   ✓ should be strictly equal
> 
>   ✓ should be strictly equal
> 
>   ✓ should be strictly equal
> 
>   ✓ should be strictly equal
> 
>   ✓ should be strictly equal
> 
>   ✓ should be strictly equal
> 
>   ✓ should be strictly equal
> test/inspect.js
> 
>   ✓ should be strictly equal
> 
>   ✓ should be deeply equivalent
> 
>   ✓ should be deeply equivalent
> 
>   ✓ should be deeply equivalent
> 
>   ✓ should be deeply equivalent
> 
>   ✓ should be deeply equivalent
> test/opts.js
> 
>   ✓ should be deeply equivalent
> 
>   ✓ should be deeply equivalent
> 
>   ✓ should be deeply equivalent
> 
>   ✓ should be deeply equivalent
> 
>   ✓ should be deeply equivalent
> 
>   ✓ should be deeply equivalent
> 
>   ✓ should be deeply equivalent
> 
>   ✓ should be deeply equivalent
> 
>   ✓ should be deeply equivalent
> 
>   ✓ should be deeply equivalent
> 
>   ✓ should be deeply equivalent
> 
>   ✓ should be deeply equivalent
> 
>   ✓ should be deeply equivalent
> 
>   ✓ should be deeply equivalent
> 
>   ✓ should be deeply equivalent
> 
>   ✓ should be deeply equivalent
> 
>   ✓ should be deeply equivalent
> 
>   ✓ should be deeply equivalent
> 
>   ✓ should be deeply equivalent
> 
>   ✓ should be deeply equivalent
> test/parent.js
> 
>   ✓ should be strictly equal
> 
>   ✓ should be strictly equal
> 
>   ✓ should be strictly equal
> 
>   ✓ should be strictly equal
> 
>   ✓ should be strictly equal
> 
>   74 passing (2s)
> ERROR: Coverage for lines (98%) does not meet global threshold (100%)
> ERROR: Coverage for functio

Bug#1009558: node-convert-source-map: FTBFS: ERROR: Coverage for statements (98.55%) does not meet global threshold (100%)

[Lucas Nussbaum]

Source: node-convert-source-map
Version: 1.8.0+~1.5.2-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
> Link node_modules/@types/convert-source-map -> ../../types-convert-source-map
>dh_auto_build --buildsystem=nodejs
> No build command found, searching known files
> No build command found, searching known files
>dh_auto_test --buildsystem=nodejs
>   ln -s ../. node_modules/convert-source-map
>   /bin/sh -ex debian/tests/pkg-js/test
> + tap -R spec test/comment-regex.js test/convert-source-map.js 
> test/map-file-comment.js
> 
> (node:3380862) DeprecationWarning: deepEqual() is deprecated, use same() 
> instead
> (Use `node --trace-deprecation ...` to show where the warning was created)
> test/comment-regex.js
>   comment regex old spec - @
> 
> ✓ matches //@
> 
> ✓ matches //@  with charset
> 
> ✓ matches //@  with charset
> 
> ✓ matches   //@
> 
> ✓ matches   //@  with charset
> 
> ✓ matches   //@  with charset
> 
> ✓ matches   //@
> 
> ✓ matches   //@  with charset
> 
> ✓ matches   //@  with charset
> 
> ✓ matches //@
> 
> ✓ matches //@  with charset
> 
> ✓ matches //@  with charset
> 
> ✓ matches /*@
> 
> ✓ matches /*@  with charset
> 
> ✓ matches /*@  with charset
> 
> ✓ matches   /*@
> 
> ✓ matches   /*@  with charset
> 
> ✓ matches   /*@  with charset
> 
> ✓ matches   /*@
> 
> ✓ matches   /*@  with charset
> 
> ✓ matches   /*@  with charset
> 
> ✓ matches /*@
> 
> ✓ matches /*@  with charset
> 
> ✓ matches /*@  with charset
> 
> ✓ should not match  @// @
> 
> ✓ should not match  @/* @
> 
>   comment regex new spec - #
> 
> ✓ matches   //\#
> 
> ✓ matches   //\#  with charset
> 
> ✓ matches   //\#  with charset
> 
> ✓ matches   //\#
> 
> ✓ matches   //\#  with charset
> 
> ✓ matches   //\#  with charset
> 
> ✓ matches //\#
> 
> ✓ matches //\#  with charset
> 
> ✓ matches //\#  with charset
> 
> ✓ matches /*\#
> 
> ✓ matches /*\#  with charset
> 
> ✓ matches /*\#  with charset
> 
> ✓ matches   /*\#
> 
> ✓ matches   /*\#  with charset
> 
> ✓ matches   /*\#  with charset
> 
> ✓ matches   /*\#
> 
> ✓ matches   /*\#  with charset
> 
> ✓ matches   /*\#  with charset
> 
> ✓ matches /*\#
> 
> ✓ matches /*\#  with charset
> 
> ✓ matches /*\#  with charset
> 
> ✓ should not match  \#// \#
> 
> ✓ should not match  \#/* \#
> 
>   mapFileComment regex old spec - @
> 
> (node:3380861) DeprecationWarning: deepEqual() is deprecated, use same() 
> instead
> (Use `node --trace-deprecation ...` to show where the warning was created)
> ✓ matches //@  ::
> 
> ✓ matches   //@  ::
> (node:3380861) DeprecationWarning: similar() is deprecated, use match() 
> instead
> 
> ✓ matches   //@  ::
> 
> ✓ matches ///@  ::
> 
> ✓ matches ;//@  ::
> 
> ✓ matches return//@  ::
> 
> ✓ does not match  @// @ ::
> 
> ✓ does not match var sm = `//@  :: `
> 
> ✓ does not match var sm = "//@  :: "
> 
> ✓ does not match var sm = '//@  :: '
> 
> ✓ does not match var sm = ' //@  :: '
> 
>   mapFileComment regex new spec - #
> 
> ✓ matches //\#  ::
> 
> ✓ matches   //\#  ::
> 
> ✓ matches   //\#  ::
> 
> ✓ matches ///\#  ::
> 
> ✓ matches ;//\#  ::
> 
> ✓ matches return//\#  ::
> 
> ✓ does not match  \#// \# ::
> 
> ✓ does not match var sm = `//\#  :: `
> 
> ✓ does not match var sm = "//\#  :: "
> 
> ✓ does not match var sm = '//\#  :: '
> 
> ✓ does not match var sm = ' //\#  :: '
> 
>   mapFileComment regex /* */ old spec - @
> 
> ✓ matches /*@  :: */
> 
> ✓ matches   /*@  ::   */
> 
> ✓ matches   /*@  ::*/
> 
> ✓ matches leading string/*@  :: */
> 
> ✓ matches /*@  ::*/
> 
> ✓ does not match /*@  ::  */ */
> 
> ✓ does not match /*@  ::  */ more text
> 
>   mapFileComment regex /* */ new spec - #
> 
> ✓ matches /*\#  :: */
> 
> ✓ matches   /*\# 

Bug#1009557: node-lynx: FTBFS: ERROR: Coverage for statements (86.25%) does not meet global threshold (100%)

[Lucas Nussbaum]

Source: node-lynx
Version: 0.2.1-4
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/lynx
>   /bin/sh -ex debian/tests/pkg-js/test
> + tap tests/counts-test.js tests/errors-test.js tests/gauges-test.js 
> tests/sampling-test.js tests/scopes-test.js tests/sets-test.js 
> tests/stream-test.js tests/timings-test.js
> TAP version 13
> (node:3974192) [DEP0005] DeprecationWarning: Buffer() is deprecated due to 
> security and usability issues. Please use the Buffer.alloc(), 
> Buffer.allocUnsafe(), or Buffer.from() methods instead.
> (Use `node --trace-deprecation ...` to show where the warning was created)
> (node:3974166) [DEP0005] DeprecationWarning: Buffer() is deprecated due to 
> security and usability issues. Please use the Buffer.alloc(), 
> Buffer.allocUnsafe(), or Buffer.from() methods instead.
> (Use `node --trace-deprecation ...` to show where the warning was created)
> (node:3974178) [DEP0005] DeprecationWarning: Buffer() is deprecated due to 
> security and usability issues. Please use the Buffer.alloc(), 
> Buffer.allocUnsafe(), or Buffer.from() methods instead.
> (Use `node --trace-deprecation ...` to show where the warning was created)
> (node:3974169) [DEP0005] DeprecationWarning: Buffer() is deprecated due to 
> security and usability issues. Please use the Buffer.alloc(), 
> Buffer.allocUnsafe(), or Buffer.from() methods instead.
> (Use `node --trace-deprecation ...` to show where the warning was created)
> (node:3974167) [DEP0005] DeprecationWarning: Buffer() is deprecated due to 
> security and usability issues. Please use the Buffer.alloc(), 
> Buffer.allocUnsafe(), or Buffer.from() methods instead.
> (Use `node --trace-deprecation ...` to show where the warning was created)
> (node:3974168) [DEP0005] DeprecationWarning: Buffer() is deprecated due to 
> security and usability issues. Please use the Buffer.alloc(), 
> Buffer.allocUnsafe(), or Buffer.from() methods instead.
> (Use `node --trace-deprecation ...` to show where the warning was created)
> (node:3974170) [DEP0005] DeprecationWarning: Buffer() is deprecated due to 
> security and usability issues. Please use the Buffer.alloc(), 
> Buffer.allocUnsafe(), or Buffer.from() methods instead.
> (Use `node --trace-deprecation ...` to show where the warning was created)
> ok 1 - tests/counts-test.js # time=1023.256ms {
> # Subtest: counts test
> ok 1 - Equality check for foo.bar:1|c
> ok 2 - Equality check for uno:-1|c two:-1|c trezentos:-1|c
> ok 3 - Equality check for boaz:101|c
> ok 4 - Equality check for foo.baz:-1|c
> 1..4
> ok 1 - counts test # time=36.295ms
> 
> 1..1
> # time=1023.256ms
> }
> 
> ok 2 - tests/errors-test.js # time=23.272ms {
> # Subtest: errors
> ok 1 - should have a reference to the function
> ok 2 - args should be supplied
> ok 3 - should be equal
> ok 4 - should have a reference to the function
> ok 5 - args should be supplied
> ok 6 - should be equal
> ok 7 - should have a reference to the function
> ok 8 - args should be supplied
> ok 9 - should be equal
> 1..9
> ok 1 - errors # time=15.925ms
> 
> 1..1
> # time=23.272ms
> }
> 
> not ok 3 - tests/gauges-test.js # time=1014.937ms
>   ---
>   env: {}
>   file: tests/gauges-test.js
>   timeout: 3
>   command: /usr/bin/node
>   args:
> - tests/gauges-test.js
>   stdio:
> - 0
> - pipe
> - 2
>   cwd: /<>
>   exitCode: 1
>   ...
> {
> # Subtest: gauges test
> not ok 1 - bind EADDRINUSE 127.0.0.1:9753
>   ---
>   at:
> line: 357
> column: 20
> file: dgram.js
> function: GetAddrInfoReqWrap.callback
>   errno: -98
>   code: EADDRINUSE
>   syscall: bind
>   address: 127.0.0.1
>   port: 9753
>   tapCaught: uncaughtException
>   test: gauges test
>   ...
> 
> 1..1
> # failed 1 test
> not ok 1 - gauges test # time=36.039ms
> 
> 1..1
> # failed 1 test
> # time=1014.937m

Bug#1009556: node-invariant: FTBFS: ERROR: Coverage for statements (81.25%) does not meet global threshold (100%)

[Lucas Nussbaum]

Source: node-invariant
Version: 2.2.4-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
> Link node_modules/@types/invariant -> ../../types-invariant
>dh_auto_build --buildsystem=nodejs
> No build command found, searching known files
> No build command found, searching known files
>dh_auto_test --buildsystem=nodejs
>   ln -s ../. node_modules/invariant
>   /bin/sh -ex debian/tests/pkg-js/test
> + NODE_ENV=production tap test/test.js
> TAP version 13
> ok 1 - test/test.js # time=395.807ms {
> # Subtest: node
> 1..4
> ok 1 - expected to not throw
> ok 2 - expected to throw
> ok 3 - expected to not throw
> ok 4 - expected to throw
> ok 1 - node # time=390.236ms
> 
> 1..1
> # time=395.807ms
> }
> 
> 1..1
> # time=817.515ms
> ERROR: Coverage for lines (81.25%) does not meet global threshold (100%)
> ERROR: Coverage for functions (50%) does not meet global threshold (100%)
> ERROR: Coverage for branches (62.5%) does not meet global threshold (100%)
> ERROR: Coverage for statements (81.25%) does not meet global threshold (100%)
> --|-|--|-|-|---
> File  | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s 
> --|-|--|-|-|---
> All files |   81.25 | 62.5 |  50 |   81.25 |   
>  invariant.js |   81.25 | 62.5 |  50 |   81.25 | 25-26,41  
> --|-|--|-|-|---
> 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-invariant_2.2.4-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.

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

[Lucas Nussbaum]

Source: node-ini
Version: 2.0.1-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/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=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.

Bug#1009553: node-isexe: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1

[Lucas Nussbaum]

Source: node-isexe
Version: 2.0.0+~2.0.1-4
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
> Link node_modules/@types/isexe -> ../../types-isexe
>dh_auto_build --buildsystem=nodejs
> No build command found, searching known files
> No build command found, searching known files
>dh_auto_test --buildsystem=nodejs
>   ln -s ../. node_modules/isexe
>   /bin/sh -ex debian/tests/pkg-js/test
> + tap -R test/basic.js --branches=100 --statements=100 --functions=100 
> --lines=100
> Error: Cannot find module 'test/basic.js'
> Require stack:
> - /usr/share/nodejs/caller-callsite/noop.js
> at Function.Module._resolveFilename 
> (internal/modules/cjs/loader.js:902:15)
> at resolveFileName (/usr/share/nodejs/resolve-from/index.js:29:39)
> at resolveFrom (/usr/share/nodejs/resolve-from/index.js:43:9)
> at module.exports (/usr/share/nodejs/resolve-from/index.js:46:47)
> at importJsx (/usr/share/nodejs/@isaacs/import-jsx/index.js:20:21)
> at Object. (/usr/share/nodejs/tap/bin/run.js:464:46)
> at runTests (/usr/share/nodejs/tap/bin/run.js:774:3)
> at mainAsync (/usr/share/nodejs/tap/bin/run.js:267:5) {
>   code: 'MODULE_NOT_FOUND',
>   requireStack: [ '/usr/share/nodejs/caller-callsite/noop.js' ]
> }
> TAP version 13
> 1..0
> # time=2.767ms
> --|-|--|-|-|---
> File  | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s 
> --|-|--|-|-|---
> All files |   0 |0 |   0 |   0 |   
> --|-|--|-|-|---
> 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-isexe_2.0.0+~2.0.1-4_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.

Bug#1009554: node-json-parse-better-errors: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1

[Lucas Nussbaum]

Source: node-json-parse-better-errors
Version: 1.0.2+~cs3.3.1-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
> Link node_modules/json-parse-even-better-errors -> 
> ../json-parse-even-better-errors
> Link node_modules/@types/json-parse-better-errors -> 
> ../../types-json-parse-better-errors
>dh_auto_build --buildsystem=nodejs
> No build command found, searching known files
> No build command found, searching known files
> No build command found, searching known files
>dh_auto_test --buildsystem=nodejs
>   ln -s ../. node_modules/json-parse-better-errors
>   cd ./json-parse-even-better-errors && sh -ex 
> ../debian/nodejs/json-parse-even-better-errors/test
> + tap -J test/index.js
> TAP version 13
> (node:3398291) DeprecationWarning: deepEqual() is deprecated, use same() 
> instead
> (Use `node --trace-deprecation ...` to show where the warning was created)
> (node:3398291) DeprecationWarning: isa() is deprecated, use type() instead
> ok 1 - test/index.js # time=198.213ms {
> # Subtest: parses JSON
> 1..6
> ok 1 - object
> ok 2 - array
> ok 3 - num
> ok 4 - null
> ok 5 - true
> ok 6 - false
> ok 1 - parses JSON # time=16.883ms
> 
> # Subtest: preserves indentation and newline styles
> # Subtest: {"type":"object","newline":"\n","indent":""}
> ok 1 - preserved newline
> ok 2 - preserved indent
> 1..2
> ok 1 - {"type":"object","newline":"\\n","indent":""} # time=1.389ms
> 
> # Subtest: {"type":"array","newline":"\n","indent":""}
> ok 1 - preserved newline
> ok 2 - preserved indent
> 1..2
> ok 2 - {"type":"array","newline":"\\n","indent":""} # time=1.004ms
> 
> # Subtest: {"type":"object","newline":"\n","indent":"  "}
> ok 1 - preserved newline
> ok 2 - preserved indent
> 1..2
> ok 3 - {"type":"object","newline":"\\n","indent":"  "} # time=0.938ms
> 
> # Subtest: {"type":"array","newline":"\n","indent":"  "}
> ok 1 - preserved newline
> ok 2 - preserved indent
> 1..2
> ok 4 - {"type":"array","newline":"\\n","indent":"  "} # time=0.939ms
> 
> # Subtest: {"type":"object","newline":"\n","indent":"\t"}
> ok 1 - preserved newline
> ok 2 - preserved indent
> 1..2
> ok 5 - {"type":"object","newline":"\\n","indent":"\\t"} # time=0.822ms
> 
> # Subtest: {"type":"array","newline":"\n","indent":"\t"}
> ok 1 - preserved newline
> ok 2 - preserved indent
> 1..2
> ok 6 - {"type":"array","newline":"\\n","indent":"\\t"} # time=0.893ms
> 
> # Subtest: {"type":"object","newline":"\n","indent":" \t \t "}
> ok 1 - preserved newline
> ok 2 - preserved indent
> 1..2
> ok 7 - {"type":"object","newline":"\\n","indent":" \\t \\t "} # 
> time=0.589ms
> 
> # Subtest: {"type":"array","newline":"\n","indent":" \t \t "}
> ok 1 - preserved newline
> ok 2 - preserved indent
> 1..2
> ok 8 - {"type":"array","newline":"\\n","indent":" \\t \\t "} # 
> time=0.622ms
> 
> # Subtest: {"type":"object","newline":"\r\n&

Bug#1009552: node-asn1: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1

[Lucas Nussbaum]

Source: node-asn1
Version: 0.2.6+~0.2.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
> Link node_modules/@types/asn1 -> ../../types-asn1
>dh_auto_build --buildsystem=nodejs
> No build command found, searching known files
> No build command found, searching known files
>dh_auto_test --buildsystem=nodejs
>   ln -s ../. node_modules/asn1
>   /bin/sh -ex debian/tests/pkg-js/test
> + tap ./tst
> TAP version 13
> not ok 1 - ./tst # time=25.266ms {
> not ok 1 - ENOENT: no such file or directory, stat './tst'
>   ---
>   stack: |
> runAllFiles (/usr/share/nodejs/tap/bin/run.js:652:15)
> runTests (/usr/share/nodejs/tap/bin/run.js:783:3)
> mainAsync (/usr/share/nodejs/tap/bin/run.js:267:5)
> main (/usr/share/nodejs/tap/bin/run.js:141:3)
> Object.j.main (/usr/share/nodejs/jackspeak/index.js:483:5)
> execute (/usr/share/nodejs/jackspeak/index.js:224:7)
> jack (/usr/share/nodejs/jackspeak/index.js:163:31)
> module.exports (/usr/share/nodejs/tap/bin/jack.js:28:26)
> Object. (/usr/share/nodejs/tap/bin/run.js:874:23)
>   at:
> line: 1131
> column: 3
> file: fs.js
> function: Object.statSync
>   errno: -2
>   syscall: stat
>   code: ENOENT
>   path: ./tst
>   test: ./tst
>   ...
> 
> 1..1
> # failed 1 test
> }
> 
> 1..1
> # failed 1 test
> # time=55.669ms
> --|-|--|-|-|---
> File  | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s 
> --|-|--|-|-|---
> All files |   0 |0 |   0 |   0 |   
> --|-|--|-|-|---
> 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-asn1_0.2.6+~0.2.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.

Bug#1009551: node-csstype: FTBFS: src/utils/logger.ts(6,53): error TS2339: Property 'magenta' does not exist on type 'typeof import("/usr/share/nodejs/chalk/source/index")'.

[Lucas Nussbaum]

Source: node-csstype
Version: 3.0.11-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):
> make[1]: Entering directory '/<>'
> ts-node --files build.ts --start
> Generating...
> src/utils/logger.ts(6,53): error TS2339: Property 'magenta' does not exist on 
> type 'typeof import("/usr/share/nodejs/chalk/source/index")'.
> src/utils/logger.ts(10,52): error TS2339: Property 'yellow' does not exist on 
> type 'typeof import("/usr/share/nodejs/chalk/source/index")'.
> 
> make[1]: *** [debian/rules:7: override_dh_auto_build] Error 1


The full build log is available from:
http://qa-logs.debian.net/2022/04/12/node-csstype_3.0.11-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.

Bug#1009550: node-stable: FTBFS: make[1]: *** [debian/rules:8: override_dh_auto_build] Error 243

[Lucas Nussbaum]

Source: node-stable
Version: 0.1.8-2
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 --with nodejs
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure --buildsystem=nodejs
>debian/rules override_dh_auto_build
> make[1]: Entering directory '/<>'
> npm run prepare
> 
> make[1]: *** [debian/rules:8: override_dh_auto_build] Error 243


The full build log is available from:
http://qa-logs.debian.net/2022/04/12/node-stable_0.1.8-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=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.

Bug#1009548: node-are-we-there-yet: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1

[Lucas Nussbaum]

Source: node-are-we-there-yet
Version: 3.0.0+~1.1.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
> Link node_modules/@types/are-we-there-yet -> ../../types-are-we-there-yet
>dh_auto_build --buildsystem=nodejs
> No build command found, searching known files
> No build command found, searching known files
>dh_auto_test --buildsystem=nodejs
>   ln -s ../. node_modules/are-we-there-yet
>   /bin/sh -ex debian/tests/pkg-js/test
> + tap test/*.js
> TAP version 13
> not ok 1 - test/*.js # time=18.999ms {
> not ok 1 - ENOENT: no such file or directory, stat 'test/*.js'
>   ---
>   stack: |
> runAllFiles (/usr/share/nodejs/tap/bin/run.js:652:15)
> runTests (/usr/share/nodejs/tap/bin/run.js:783:3)
> mainAsync (/usr/share/nodejs/tap/bin/run.js:267:5)
> main (/usr/share/nodejs/tap/bin/run.js:141:3)
> Object.j.main (/usr/share/nodejs/jackspeak/index.js:483:5)
> execute (/usr/share/nodejs/jackspeak/index.js:224:7)
> jack (/usr/share/nodejs/jackspeak/index.js:163:31)
> module.exports (/usr/share/nodejs/tap/bin/jack.js:28:26)
> Object. (/usr/share/nodejs/tap/bin/run.js:874:23)
>   at:
> line: 1131
> column: 3
> file: fs.js
> function: Object.statSync
>   errno: -2
>   syscall: stat
>   code: ENOENT
>   path: test/*.js
>   test: test/*.js
>   ...
> 
> 1..1
> # failed 1 test
> }
> 
> 1..1
> # failed 1 test
> # time=43.602ms
> --|-|--|-|-|---
> File  | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s 
> --|-|--|-|-|---
> All files |   0 |0 |   0 |   0 |   
> --|-|--|-|-|---
> 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-are-we-there-yet_3.0.0+~1.1.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.

Bug#1009547: node-stream-browserify: FTBFS: ERROR: Coverage for statements (24.07%) does not meet global threshold (100%)

[Lucas Nussbaum]

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.

Bug#1009546: node-browserify-zlib: FTBFS: ERROR: Coverage for statements (89.57%) does not meet global threshold (100%)

[Lucas Nussbaum]

Source: node-browserify-zlib
Version: 0.2.0+20170820git8b3f0a862f6b+dfsg-6
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):
> make[1]: Entering directory '/<>'
> babeljs src/ --out-dir lib
> Successfully compiled 2 files with Babel (407ms).
> make[1]: Leaving directory '/<>'
>dh_auto_test --buildsystem=nodejs
>   mkdir -p node_modules
>   ln -s ../. node_modules/browserify-zlib
>   /bin/sh -ex debian/tests/pkg-js/test
> + convert rose: test/fixtures/person.jpg
> + gzip -9 -n
> + tap -R spec test/test-zlib-close-after-error.js 
> test/test-zlib-close-after-write.js test/test-zlib-const.js 
> test/test-zlib-convenience-methods.js test/test-zlib-dictionary-fail.js 
> test/test-zlib-dictionary.js test/test-zlib-flush-drain.js 
> test/test-zlib-flush-flags.js test/test-zlib-from-concatenated-gzip.js 
> test/test-zlib-from-gzip.js test/test-zlib-from-string.js 
> test/test-zlib-invalid-input.js test/test-zlib-random-byte-pipes.js 
> test/test-zlib-sync-no-event.js test/test-zlib-truncated.js 
> test/test-zlib-unzip-one-byte-chunks.js test/test-zlib-write-after-close.js 
> test/test-zlib-write-after-flush.js test/test-zlib-zero-byte.js 
> test/test-zlib.js
> 
> test/test-zlib-close-after-error.js
>   - test/test-zlib-close-after-error.js
> test/test-zlib-close-after-write.js
>   - test/test-zlib-close-after-write.js
> test/test-zlib-const.js
>   - test/test-zlib-const.js
> test/test-zlib-convenience-methods.js
>   - test/test-zlib-convenience-methods.js
> test/test-zlib-dictionary-fail.js
>   - test/test-zlib-dictionary-fail.js
> test/test-zlib-dictionary.js
>   - test/test-zlib-dictionary.js
> test/test-zlib-flush-drain.js
>   - test/test-zlib-flush-drain.js
> test/test-zlib-flush-flags.js
>   - test/test-zlib-flush-flags.js
> Doing the non-strings
> assert.js:118
>   throw new AssertionError(obj);
>   ^
> 
> AssertionError [ERR_ASSERTION]: Got unwanted exception.
> Actual message: "The "chunk" argument must be of type string or an instance 
> of Buffer or Uint8Array. Received type number (1)"
> at /<>/test/test-zlib-invalid-input.js:13:10
> at Array.forEach ()
> at Object. 
> (/<>/test/test-zlib-invalid-input.js:11:17)
> at Module._compile (internal/modules/cjs/loader.js:1085:14)
> at Module.replacementCompile 
> (/usr/share/nodejs/append-transform/index.js:60:13)
> at Module._extensions..js (internal/modules/cjs/loader.js:1114:10)
> at Object. (/usr/share/nodejs/append-transform/index.js:64:4)
> at Module.load (internal/modules/cjs/loader.js:950:32)
> at Function.Module._load (internal/modules/cjs/loader.js:790:12)
> at Function.executeUserEntryPoint [as runMain] 
> (internal/modules/run_main.js:75:12) {
>   generatedMessage: false,
>   code: 'ERR_ASSERTION',
>   actual: TypeError [ERR_INVALID_ARG_TYPE]: The "chunk" argument must be of 
> type string or an instance of Buffer or Uint8Array. Received type number (1)
>   at new NodeError (internal/errors.js:322:7)
>   at Gunzip.Writable.write (internal/streams/writable.js:285:13)
>   at Gunzip.Writable.end (internal/streams/writable.js:567:10)
>   at zlibBuffer (/<>/lib/index.js:11:4004)
>   at Object.exports.gunzip (/<>/lib/index.js:11:2960)
>   at /<>/test/test-zlib-invalid-input.js:14:10
>   at getActual (assert.js:753:5)
>   at Function.doesNotThrow (assert.js:919:32)
>   at /<>/test/test-zlib-invalid-input.js:13:10
>   at Array.forEach () {
> code: 'ERR_INVALID_ARG_TYPE'
>   },
>   expected: undefined,
>   operator: 'doesNotThrow'
> }
> block=249
> remain=775
> 
> inp data 249
> gzip data 10
> block=260
> remain=515
> 
> inp data 260
> block=252
> remain=263
> 
> inp data 252
> block=251
> remain=12
> 
> inp data 251
> block=12
> remain=0
> 
> inp data 12
> (node:1322272) [DEP0005] DeprecationWarning: Buffer() is deprecated due to 
> security and usability issues. Please use the Buffer.alloc(), 
> Buffer.allocUnsafe(), or Buffer.from() methods instead.
> (Use `node --trace-deprecation ...` to show where the warning was created)
> gzip data 1037
> gunz data 1024
> out data 40
> hash=8f61a164c25fb8be3d1db8a1df66cea056027709
> test/test-zlib-from-concatenated-gzip.js
>   - test/test-zlib-from-concatenated-gzip.js
> test/test-zlib-from-gzip.js
>   - test/test-zlib-from-gzip.js
> test/test-zlib-from-string.js

Bug#1009545: node-jsonstream: FTBFS: ERROR: Coverage for statements (50.89%) does not meet global threshold (100%)

[Lucas Nussbaum]

Source: node-jsonstream
Version: 1.3.5-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 --with nodejs
>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/JSONStream
>   /bin/sh -ex debian/tests/pkg-js/test
> + tap test/browser.js test/map.js test/null.js
> TAP version 13
> ok 1 - test/browser.js # time=952.625ms {
> # basic parsing
> ok 1 should be strictly equal
> ok 2 should be strictly equal
> 
> 1..2
> # tests 2
> # pass  2
> 
> # ok
> }
> 
> ok 2 - test/map.js # time=888.325ms {
> # map function
> ok 1 should be deeply equivalent
> # filter function
> ok 2 should be deeply equivalent
> 
> 1..2
> # tests 2
> # pass  2
> 
> # ok
> }
> 
> ok 3 - test/null.js # time=917.129ms {
> # null properties
> ok 1 should be deeply equivalent
> 
> 1..1
> # tests 1
> # pass  1
> 
> # ok
> }
> 
> 1..3
> # time=976.145ms
> ERROR: Coverage for lines (52.25%) does not meet global threshold (100%)
> ERROR: Coverage for functions (56.25%) does not meet global threshold (100%)
> ERROR: Coverage for branches (54.16%) does not meet global threshold (100%)
> ERROR: Coverage for statements (50.89%) does not meet global threshold (100%)
> --|-|--|-|-|
> File  | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s
>   
> --|-|--|-|-|
> All files |   50.89 |54.16 |   56.25 |   52.25 |  
>   
>  index.js |   50.89 |54.16 |   56.25 |   52.25 | 
> ...115,132,140-142,166,169-171,175-210,214-244 
> --|-|--|-|-|
> 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-jsonstream_1.3.5-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.

Bug#1009544: node-combine-source-map: FTBFS: ERROR: Coverage for statements (93.44%) does not meet global threshold (100%)

[Lucas Nussbaum]

Source: node-combine-source-map
Version: 0.8.0+ds-7
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/combine-source-map
>   /bin/sh -ex debian/tests/pkg-js/test
> + tap test/combine-source-map.js
> TAP version 13
> (node:261468) DeprecationWarning: deepEqual() is deprecated, use same() 
> instead
> (Use `node --trace-deprecation ...` to show where the warning was created)
> ok 1 - test/combine-source-map.js # time=108.757ms {
> # Subtest: add one file with inlined source
> ok 1 - all generated lines are offset properly and columns unchanged
> ok 2 - all original lines and columns are unchanged
> ok 3 - includes the original source
> ok 4 - includes original filename
> 1..4
> ok 1 - add one file with inlined source # time=46.326ms
> 
> # Subtest: add one file without inlined source
> ok 1 - includes the generated source
> ok 2 - includes generated filename
> ok 3 - generates mappings offset by the given line
> 1..3
> ok 2 - add one file without inlined source # time=13.806ms
> 
> # Subtest: add one file with inlined sources from multiple files
> ok 1 - include the correct source
> ok 2 - include the correct source file content
> ok 3 - should properly map multiple files
> 1..3
> ok 3 - add one file with inlined sources from multiple files # 
> time=7.594ms
> 
> # Subtest: relative path from multiple files
> ok 1 - include the correct source
> ok 2 - include the correct source file content
> ok 3 - should properly map multiple files
> 1..3
> ok 4 - relative path from multiple files # time=6.142ms
> 
> # Subtest: relative path when source and file name are the same
> ok 1 - include the correct source
> ok 2 - should properly map multiple files
> 1..2
> ok 5 - relative path when source and file name are the same # time=2.22ms
> 
> # Subtest: remove comments
> ok 1 - should be equal
> ok 2 - should be equal
> ok 3 - should be equal
> ok 4 - should be equal
> 1..4
> ok 6 - remove comments # time=1.587ms
> 
> 1..6
> # time=108.757ms
> }
> 
> 1..1
> # time=1067.475ms
> ERROR: Coverage for lines (96.29%) does not meet global threshold (100%)
> ERROR: Coverage for functions (93.33%) does not meet global threshold (100%)
> ERROR: Coverage for branches (78.78%) does not meet global threshold (100%)
> ERROR: Coverage for statements (93.44%) does not meet global threshold (100%)
> --|-|--|-|-|---
> File  | % Stmts | % Branch | % Funcs | % 
> Lines | Uncovered Line #s 
> --|-|--|-|-|---
> All files |   93.44 |78.78 |   93.33 |   
> 96.29 |   
>  node-combine-source-map-0.8.0+ds |   92.59 |82.75 |92.3 |   
> 95.74 |   
>   index.js|   92.59 |82.75 |92.3 |   
> 95.74 | 31,134
>  node-combine-source-map-0.8.0+ds/lib | 100 |   50 | 100 | 
> 100 |   
>   mappings-from-map.js| 100 |   50 | 100 | 
> 100 | 16-24 
> --|-|--|-|-|---
> 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-combine-source-map_0.8.0+ds-7_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.de

Bug#1009543: node-callback-stream: FTBFS: ERROR: Coverage for branches (83.33%) does not meet global threshold (100%)

[Lucas Nussbaum]

Source: node-callback-stream
Version: 1.1.0-3
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 --with nodejs
>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/callback-stream
>   /bin/sh -ex debian/tests/pkg-js/test
> + tap test.js
> TAP version 13
> (node:537207) DeprecationWarning: deepEqual() is deprecated, use same() 
> instead
> (Use `node --trace-deprecation ...` to show where the warning was created)
> ok 1 - test.js # time=29.659ms {
> # Subtest: call the callback after end with object mode
> ok 1 - should return the ending value
> 1..1
> ok 1 - call the callback after end with object mode # time=15ms
> 
> # Subtest: support multiple writes with object mode
> ok 1 - should return the ending value
> 1..1
> ok 2 - support multiple writes with object mode # time=2.455ms
> 
> # Subtest: works without object mode
> ok 1 - should contain only one value
> ok 2 - should return the ending value
> 1..2
> ok 3 - works without object mode # time=1.26ms
> 
> # Subtest: is pipeable
> ok 1 - should have the same content of the file
> 1..1
> ok 4 - is pipeable # time=4.084ms
> 
> # Subtest: callback.obj shortcut for objectMode
> ok 1 - should return the ending value
> 1..1
> ok 5 - callback.obj shortcut for objectMode # time=1.302ms
> 
> 1..5
> # time=29.659ms
> }
> 
> 1..1
> # time=716.531ms
> ERROR: Coverage for branches (83.33%) does not meet global threshold (100%)
> --|-|--|-|-|---
> File  | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s 
> --|-|--|-|-|---
> All files | 100 |83.33 | 100 | 100 |   
>  index.js | 100 |83.33 | 100 | 100 | 41
> --|-|--|-|-|---
> 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-callback-stream_1.1.0-3_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.

Bug#1009542: node-libravatar: FTBFS: ERROR: Coverage for statements (80.19%) does not meet global threshold (100%)

[Lucas Nussbaum]

Source: node-libravatar
Version: 3.0.0-2
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/libravatar
>   /bin/sh -ex debian/tests/pkg-js/test
> + tap tests/federation.js tests/url.js
> TAP version 13
> ok 1 - tests/federation.js # time=26.174ms {
> # Subtest: sanitization of invalid SRV responses
> ok 1 - both parameters missing
> ok 2 - first parameter missing
> ok 3 - second parameter missing
> ok 4 - port too small
> ok 5 - port too big
> ok 6 - invalid hostname
> ok 7 - invalid port
> 1..7
> ok 1 - sanitization of invalid SRV responses # time=5.915ms
> 
> # Subtest: sanitization of valid SRV responses
> ok 1 - normal http
> ok 2 - normal https
> ok 3 - weird http
> ok 4 - weird https
> 1..4
> ok 2 - sanitization of valid SRV responses # time=1.491ms
> 
> # Subtest: ordering of invalid SRV hostnames
> ok 1 - empty array [0]
> ok 2 - empty array [1]
> ok 3 - single empty array [0]
> ok 4 - single empty array [1]
> 1..4
> ok 3 - ordering of invalid SRV hostnames # time=1.166ms
> 
> # Subtest: ordering of valid SRV hostnames on priority
> ok 1 - single hostname [0]
> ok 2 - single hostname [1]
> ok 3 - two hostnames [0]
> ok 4 - two hostnames [1]
> ok 5 - four hostnames [0]
> ok 6 - four hostnames [1]
> 1..6
> ok 4 - ordering of valid SRV hostnames on priority # time=1.42ms
> 
> # Subtest: ordering of valid SRV hostnames on weight
> ok 1 - random 1 [0]
> ok 2 - random 1 [1]
> ok 3 - random 2 [0]
> ok 4 - random 2 [1]
> ok 5 - random 3 [0]
> ok 6 - random 3 [1]
> ok 7 - random 4 [0]
> ok 8 - random 4 [1]
> ok 9 - random 5 [0]
> ok 10 - random 5 [1]
> 1..10
> ok 5 - ordering of valid SRV hostnames on weight # time=1.848ms
> 
> # Subtest: ordering of valid SRV hostnames on weight
> ok 1 - degenerate case
> ok 2 - simple domain over http
> ok 3 - simple domain over https
> ok 4 - longer domain over http
> 1..4
> ok 6 - ordering of valid SRV hostnames on weight # time=0.9ms
> 
> 1..6
> # time=26.174ms
> }
> 
> ok 2 - tests/url.js # time=24.161ms {
> # Subtest: parsing of user identity
> ok 1 - both parameters missing [0]
> ok 2 - both parameters missing [1]
> ok 3 - both parameters supplied [0]
> ok 4 - both parameters supplied [1]
> ok 5 - standard email [0]
> ok 6 - standard email [1]
> ok 7 - standard openid [0]
> ok 8 - standard openid [1]
> 1..8
> ok 1 - parsing of user identity # time=7.286ms
> 
> # Subtest: parsing of email address
> ok 1 - empty email [0]
> ok 2 - empty email [1]
> ok 3 - missing hostname [0]
> ok 4 - missing hostname [1]
> ok 5 - uppercase username [0]
> ok 6 - uppercase username [1]
> ok 7 - mixed-case username and hostname [0]
> ok 8 - mixed-case username and hostname [1]
> ok 9 - untrimmed email [0]
> ok 10 - untrimmed email [1]
> 1..10
> ok 2 - parsing of email address # time=1.905ms
> 
> # Subtest: parsing of openid urls
> ok 1 - empty openid [0]
> ok 2 - empty openid [1]
> ok 3 - invalid url [0]
> ok 4 - invalid url [1]
> ok 5 - mixed-case hostname [0]
> ok 6 - mixed-case hostname [1]
> ok 7 - uppercase scheme [0]
> ok 8 - uppercase scheme [1]
> ok 9 - lowercase basic auth [0]
> ok 10 - lowercase basic auth [1]
> ok 11 - mixed-case basic auth [0]
> ok 12 - mixed-case basic auth [1]
> ok 13 - sub-domain [0]
> ok 14 - sub-domain [1]
> ok 15 - https [0]
> ok 16 - https [1]
> ok 17 - uppercase path [0]
> ok 18 - uppercase path [1]
> 1..18
> ok 3 - parsing of openid u

Bug#1009541: node-lexical-scope: FTBFS: ERROR: Coverage for statements (91.11%) does not meet global threshold (100%)

[Lucas Nussbaum]

Source: node-lexical-scope
Version: 1.2.0+dfsg1-5
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/lexical-scope
>   /bin/sh -ex debian/tests/pkg-js/test
> + tap test/argument.js test/assign_implicit.js test/detect.js test/labels.js 
> test/multiple-exports.js test/named_arg.js test/obj.js test/props.js 
> test/return_hash.js test/right_hand.js test/shebang.js test/try_catch.js
> TAP version 13
> ok 1 - test/argument.js # time=1508.04ms {
> # parameters from inline arguments
> ok 1 should be deeply equivalent
> ok 2 should be deeply equivalent
> ok 3 should be deeply equivalent
> 
> 1..3
> # tests 3
> # pass  3
> 
> # ok
> }
> 
> ok 2 - test/assign_implicit.js # time=1496.997ms {
> # assign from an implicit global
> ok 1 should be deeply equivalent
> ok 2 should be deeply equivalent
> ok 3 should be deeply equivalent
> 
> 1..3
> # tests 3
> # pass  3
> 
> # ok
> }
> 
> ok 3 - test/detect.js # time=1504.281ms {
> # check locals and globals
> ok 1 should be deeply equivalent
> ok 2 should be deeply equivalent
> ok 3 should be deeply equivalent
> 
> 1..3
> # tests 3
> # pass  3
> 
> # ok
> }
> 
> ok 4 - test/labels.js # time=1489.325ms {
> # globals on the right-hand of a colon in an object literal
> ok 1 should be deeply equivalent
> ok 2 should be deeply equivalent
> ok 3 should be deeply equivalent
> 
> 1..3
> # tests 3
> # pass  3
> 
> # ok
> }
> 
> ok 5 - test/multiple-exports.js # time=1478.016ms {
> # multiple-exports
> ok 1 should be deeply equivalent
> ok 2 should be deeply equivalent
> ok 3 should be deeply equivalent
> 
> 1..3
> # tests 3
> # pass  3
> 
> # ok
> }
> 
> ok 6 - test/named_arg.js # time=1507.23ms {
> # named argument parameter
> ok 1 should be deeply equivalent
> ok 2 should be deeply equivalent
> ok 3 should be deeply equivalent
> 
> 1..3
> # tests 3
> # pass  3
> 
> # ok
> }
> 
> ok 7 - test/obj.js # time=1495.042ms {
> # globals on the right-hand of a colon in an object literal
> ok 1 should be deeply equivalent
> ok 2 should be deeply equivalent
> ok 3 should be deeply equivalent
> 
> 1..3
> # tests 3
> # pass  3
> 
> # ok
> }
> 
> ok 8 - test/props.js # time=1515.041ms {
> # implicit props: call
> ok 1 should be deeply equivalent
> ok 2 should be deeply equivalent
> ok 3 should be deeply equivalent
> # implicit props: isBuffer
> ok 4 should be deeply equivalent
> ok 5 should be deeply equivalent
> ok 6 should be deeply equivalent
> # implicit props: var
> ok 7 should be deeply equivalent
> ok 8 should be deeply equivalent
> ok 9 should be deeply equivalent
> 
> 1..9
> # tests 9
> # pass  9
> 
> # ok
> }
> 
> ok 9 - test/return_hash.js # time=365.937ms {
> # return hash
> ok 1 should be deeply equivalent
> ok 2 should be deeply equivalent
> ok 3 should be deeply equivalent
> 
> 1..3
> # tests 3
> # pass  3
> 
> # ok
> }
> 
> ok 10 - test/right_hand.js # time=349.46ms {
> # globals on the right-hand of assignment
> ok 1 should be deeply equivalent
> ok 2 should be deeply equivalent
> ok 3 should be deeply equivalent
> 
> 1..3
> # tests 3
> # pass  3
> 
> # ok
> }
> 
> ok 11 - test/shebang.js # time=359.382ms {
> # shebangs
> ok 1 should be deeply equivalent
> ok 2 should be deeply equivalent
> ok 3 should be deeply equivalent
> 
> 1..3
> # tests 3
> # pass  3
> 
> # ok
> }
> 
> ok 12 - test/try_catch.js # time=360.766ms {
> # the exception in a try catch block is a local
> ok 1 should be deeply equivalent
> ok 2 should be deeply equivalent
> ok 3 should be deeply equivalent
> 

Bug#1009540: node-prr: FTBFS: ERROR: Coverage for statements (88%) does not meet global threshold (100%)

[Lucas Nussbaum]

Source: node-prr
Version: 1.0.1-2
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/prr
>   /bin/sh -ex debian/tests/pkg-js/test
> + tap test.js
> TAP version 13
> (node:3369011) DeprecationWarning: deepEqual() is deprecated, use same() 
> instead
> (Use `node --trace-deprecation ...` to show where the warning was created)
> ok 1 - test.js # time=38.892ms {
> # Subtest: test prr(o, key, value) form
> 1..2
> ok 1 - correct value
> ok 2 - correct property descriptor
> ok 1 - test prr(o, key, value) form # time=11.008ms
> 
> # Subtest: test prr(o, { key: value }) form
> 1..2
> ok 1 - correct value
> ok 2 - correct property descriptor
> ok 2 - test prr(o, { key: value }) form # time=2.116ms
> 
> # Subtest: test multiple key:value pairs
> ok 1 - properties are not enumerable
> ok 2 - correctly set property
> ok 3 - correctly set property
> ok 4 - correctly set property
> ok 5 - correct property descriptor
> ok 6 - correct property descriptor
> ok 7 - correct property descriptor
> 1..7
> ok 3 - test multiple key:value pairs # time=4.299ms
> 
> # Subtest: test descriptor options
> ok 1 - correct value
> ok 2 - correct property descriptor
> ok 3 - correct value
> ok 4 - correct property descriptor
> ok 5 - correct value
> ok 6 - correct property descriptor
> 1..6
> ok 4 - test descriptor options # time=3.105ms
> 
> # Subtest: test descriptor options, string form
> ok 1 - correct value
> ok 2 - correct property descriptor
> ok 3 - correct value
> ok 4 - correct property descriptor
> ok 5 - correct value
> ok 6 - correct property descriptor
> 1..6
> ok 5 - test descriptor options, string form # time=2.924ms
> 
> 1..5
> # time=38.892ms
> }
> 
> 1..1
> # time=806.826ms
> ERROR: Coverage for lines (88%) does not meet global threshold (100%)
> ERROR: Coverage for functions (85.71%) does not meet global threshold (100%)
> ERROR: Coverage for branches (81.25%) does not meet global threshold (100%)
> ERROR: Coverage for statements (88%) does not meet global threshold (100%)
> --|-|--|-|-|---
> File  | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s 
> --|-|--|-|-|---
> All files |  88 |81.25 |   85.71 |  88 |   
>  prr.js   |  88 |81.25 |   85.71 |  88 | 12,21-22  
> --|-|--|-|-|---
> 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-prr_1.0.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=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.

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

[Lucas Nussbaum]

Source: node-har-validator
Version: 5.1.5-2
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/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%)
> ER