[Pkg-javascript-devel] Bug#1135433: marked as done (node-pinkie: FTBFS: Error: Timeout of 2000ms exceeded.)

Sat, 02 May 2026 00:07:14 -0700 

Your message dated Sat, 02 May 2026 07:05:20 +0000
with message-id <[email protected]>
and subject line Bug#1135433: fixed in node-pinkie 2.0.4-3
has caused the Debian Bug report #1135433,
regarding node-pinkie: FTBFS: Error: Timeout of 2000ms exceeded.
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
1135433: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1135433
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message --- 
Package: src:node-pinkie
Version: 2.0.4-2
Severity: serious
Tags: ftbfs forky sid

Dear maintainer:

During a rebuild of all packages in unstable, this package failed to build.

Below you will find the last part of the build log (probably the most
relevant part, but not necessarily). If required, the full build log
is available here:

https://people.debian.org/~sanvila/build-logs/202605/

About the archive rebuild: The build was made on virtual machines from AWS,
using sbuild and a reduced chroot with only build-essential packages.

If you cannot reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.

If this is really a bug in one of the build-depends, please use
reassign and add an affects on src:node-pinkie, so that this is still
visible in the BTS web page for this package.

Thanks.

--------------------------------------------------------------------------------
[...]
 debian/rules clean
dh clean
   dh_auto_clean --buildsystem=nodejs
        rm -rf ./node_modules/.cache ./.nyc_output
rm ./node_modules/.cache
rm ./node_modules/.cache
   dh_clean
 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

[... snipped ...]

            `then` calls `rejectPromise` synchronously
              ✔ via return from a fulfilled promise
              ✔ via return from a rejected promise
            `then` calls `rejectPromise` asynchronously
              ✔ via return from a fulfilled promise
              ✔ via return from a rejected promise
          `r` is `null`
            `then` calls `rejectPromise` synchronously
              ✔ via return from a fulfilled promise
              ✔ via return from a rejected promise
            `then` calls `rejectPromise` asynchronously
              ✔ via return from a fulfilled promise
              ✔ via return from a rejected promise
          `r` is `false`
            `then` calls `rejectPromise` synchronously
              ✔ via return from a fulfilled promise
              ✔ via return from a rejected promise
            `then` calls `rejectPromise` asynchronously
              ✔ via return from a fulfilled promise
              ✔ via return from a rejected promise
          `r` is `0`
            `then` calls `rejectPromise` synchronously
              ✔ via return from a fulfilled promise
              ✔ via return from a rejected promise
            `then` calls `rejectPromise` asynchronously
              ✔ via return from a fulfilled promise
              ✔ via return from a rejected promise
          `r` is an error
            `then` calls `rejectPromise` synchronously
              ✔ via return from a fulfilled promise
              ✔ via return from a rejected promise
            `then` calls `rejectPromise` asynchronously
              ✔ via return from a fulfilled promise
              ✔ via return from a rejected promise
          `r` is an error without a stack
            `then` calls `rejectPromise` synchronously
              ✔ via return from a fulfilled promise
              ✔ via return from a rejected promise
            `then` calls `rejectPromise` asynchronously
              ✔ via return from a fulfilled promise
              ✔ via return from a rejected promise
          `r` is a date
            `then` calls `rejectPromise` synchronously
              ✔ via return from a fulfilled promise
              ✔ via return from a rejected promise
            `then` calls `rejectPromise` asynchronously
              ✔ via return from a fulfilled promise
              ✔ via return from a rejected promise
          `r` is an object
            `then` calls `rejectPromise` synchronously
              ✔ via return from a fulfilled promise
              ✔ via return from a rejected promise
            `then` calls `rejectPromise` asynchronously
              ✔ via return from a fulfilled promise
              ✔ via return from a rejected promise
          `r` is an always-pending thenable
            `then` calls `rejectPromise` synchronously
              ✔ via return from a fulfilled promise
              ✔ via return from a rejected promise
            `then` calls `rejectPromise` asynchronously
              ✔ via return from a fulfilled promise
              ✔ via return from a rejected promise
          `r` is a fulfilled promise
            `then` calls `rejectPromise` synchronously
              ✔ via return from a fulfilled promise
              ✔ via return from a rejected promise
            `then` calls `rejectPromise` asynchronously
              ✔ via return from a fulfilled promise
              ✔ via return from a rejected promise
          `r` is a rejected promise
            `then` calls `rejectPromise` synchronously
              ✔ via return from a fulfilled promise
              ✔ via return from a rejected promise
            `then` calls `rejectPromise` asynchronously
              ✔ via return from a fulfilled promise
              ✔ via return from a rejected promise
        2.3.3.3.3: If both `resolvePromise` and `rejectPromise` are called, or 
multiple calls to the same argument are made, the first call takes precedence, 
and any further calls are ignored.
          calling `resolvePromise` then `rejectPromise`, both synchronously
            ✔ via return from a fulfilled promise
            ✔ via return from a rejected promise
          calling `resolvePromise` synchronously then `rejectPromise` 
asynchronously
            ✔ via return from a fulfilled promise
            ✔ via return from a rejected promise
          calling `resolvePromise` then `rejectPromise`, both asynchronously
            ✔ via return from a fulfilled promise
            ✔ via return from a rejected promise
          calling `resolvePromise` with an asynchronously-fulfilled promise, 
then calling `rejectPromise`, both synchronously
            ✔ via return from a fulfilled promise (51ms)
            ✔ via return from a rejected promise (50ms)
          calling `resolvePromise` with an asynchronously-rejected promise, 
then calling `rejectPromise`, both synchronously
            ✔ via return from a fulfilled promise (51ms)
            ✔ via return from a rejected promise (50ms)
          calling `rejectPromise` then `resolvePromise`, both synchronously
            ✔ via return from a fulfilled promise
            ✔ via return from a rejected promise
          calling `rejectPromise` synchronously then `resolvePromise` 
asynchronously
            ✔ via return from a fulfilled promise
            ✔ via return from a rejected promise
          calling `rejectPromise` then `resolvePromise`, both asynchronously
            ✔ via return from a fulfilled promise
            ✔ via return from a rejected promise
          calling `resolvePromise` twice synchronously
            ✔ via return from a fulfilled promise
            ✔ via return from a rejected promise
          calling `resolvePromise` twice, first synchronously then 
asynchronously
            ✔ via return from a fulfilled promise
            ✔ via return from a rejected promise
          calling `resolvePromise` twice, both times asynchronously
            ✔ via return from a fulfilled promise
            ✔ via return from a rejected promise
          calling `resolvePromise` with an asynchronously-fulfilled promise, 
then calling it again, both times synchronously
            ✔ via return from a fulfilled promise (50ms)
            ✔ via return from a rejected promise (50ms)
          calling `resolvePromise` with an asynchronously-rejected promise, 
then calling it again, both times synchronously
            ✔ via return from a fulfilled promise (51ms)
            ✔ via return from a rejected promise (50ms)
          calling `rejectPromise` twice synchronously
            ✔ via return from a fulfilled promise
            ✔ via return from a rejected promise
          calling `rejectPromise` twice, first synchronously then asynchronously
            ✔ via return from a fulfilled promise
            ✔ via return from a rejected promise
          calling `rejectPromise` twice, both times asynchronously
            ✔ via return from a fulfilled promise
            ✔ via return from a rejected promise
          saving and abusing `resolvePromise` and `rejectPromise`
            ✔ via return from a fulfilled promise (101ms)
            ✔ via return from a rejected promise (100ms)
        2.3.3.3.4: If calling `then` throws an exception `e`,
          2.3.3.3.4.1: If `resolvePromise` or `rejectPromise` have been called, 
ignore it.
            `resolvePromise` was called with a non-thenable
              ✔ via return from a fulfilled promise
              ✔ via return from a rejected promise
            `resolvePromise` was called with an asynchronously-fulfilled promise
              ✔ via return from a fulfilled promise (50ms)
              ✔ via return from a rejected promise (50ms)
            `resolvePromise` was called with an asynchronously-rejected promise
              ✔ via return from a fulfilled promise (51ms)
              ✔ via return from a rejected promise (50ms)
            `rejectPromise` was called
              ✔ via return from a fulfilled promise
              ✔ via return from a rejected promise
            `resolvePromise` then `rejectPromise` were called
              ✔ via return from a fulfilled promise
              ✔ via return from a rejected promise
            `rejectPromise` then `resolvePromise` were called
              ✔ via return from a fulfilled promise
              ✔ via return from a rejected promise
          2.3.3.3.4.2: Otherwise, reject `promise` with `e` as the reason.
            straightforward case
              ✔ via return from a fulfilled promise
              ✔ via return from a rejected promise
            `resolvePromise` is called asynchronously before the `throw`
              ✔ via return from a fulfilled promise
              ✔ via return from a rejected promise
            `rejectPromise` is called asynchronously before the `throw`
              ✔ via return from a fulfilled promise
              ✔ via return from a rejected promise
      2.3.3.4: If `then` is not a function, fulfill promise with `x`
        `then` is `5`
          ✔ via return from a fulfilled promise
          ✔ via return from a rejected promise
        `then` is an object
          ✔ via return from a fulfilled promise
          ✔ via return from a rejected promise
        `then` is an array containing a function
          ✔ via return from a fulfilled promise
          ✔ via return from a rejected promise
        `then` is a regular expression
          ✔ via return from a fulfilled promise
          ✔ via return from a rejected promise
        `then` is an object inheriting from `Function.prototype`
          ✔ via return from a fulfilled promise
          ✔ via return from a rejected promise
    2.3.4: If `x` is not an object or function, fulfill `promise` with `x`
      The value is `undefined`
        ✔ already-fulfilled
        ✔ immediately-fulfilled
        ✔ eventually-fulfilled (50ms)
        ✔ already-rejected
        ✔ immediately-rejected
        ✔ eventually-rejected (50ms)
      The value is `null`
        ✔ already-fulfilled
        ✔ immediately-fulfilled
        ✔ eventually-fulfilled (50ms)
        ✔ already-rejected
        ✔ immediately-rejected
        ✔ eventually-rejected (50ms)
      The value is `false`
        ✔ already-fulfilled
        ✔ immediately-fulfilled
        ✔ eventually-fulfilled (50ms)
        ✔ already-rejected
        ✔ immediately-rejected
        ✔ eventually-rejected (50ms)
      The value is `true`
        ✔ already-fulfilled
        ✔ immediately-fulfilled
        ✔ eventually-fulfilled (50ms)
        ✔ already-rejected
        ✔ immediately-rejected
        ✔ eventually-rejected (50ms)
      The value is `0`
        ✔ already-fulfilled
        ✔ immediately-fulfilled
        ✔ eventually-fulfilled (50ms)
        ✔ already-rejected
        ✔ immediately-rejected
        ✔ eventually-rejected (50ms)
      The value is `true` with `Boolean.prototype` modified to have a `then` 
method
        ✔ already-fulfilled
        ✔ immediately-fulfilled
        ✔ eventually-fulfilled (51ms)
        ✔ already-rejected
        ✔ immediately-rejected
        ✔ eventually-rejected (50ms)
      The value is `1` with `Number.prototype` modified to have a `then` method
        ✔ already-fulfilled
        ✔ immediately-fulfilled
        ✔ eventually-fulfilled (51ms)
        ✔ already-rejected
        ✔ immediately-rejected
        ✔ eventually-rejected (50ms)


  885 passing (19s)
  5 failing

  1) Promise.all
       should resolve empty array to empty array:
     Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure 
"done()" is called; if returning a Promise, ensure it resolves. 
(/<<PKGBUILDDIR>>/test.js)
      at createTimeoutError (/usr/share/nodejs/mocha/lib/errors.js:386:15)
      at Runnable._timeoutError (/usr/share/nodejs/mocha/lib/runnable.js:431:10)
      at Timeout.<anonymous> (/usr/share/nodejs/mocha/lib/runnable.js:246:24)
      at listOnTimeout (node:internal/timers:605:17)
      at process.processTimers (node:internal/timers:541:7)

  2) Promise.all
       should resolve values to array:
     Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure 
"done()" is called; if returning a Promise, ensure it resolves. 
(/<<PKGBUILDDIR>>/test.js)
      at createTimeoutError (/usr/share/nodejs/mocha/lib/errors.js:386:15)
      at Runnable._timeoutError (/usr/share/nodejs/mocha/lib/runnable.js:431:10)
      at Timeout.<anonymous> (/usr/share/nodejs/mocha/lib/runnable.js:246:24)
      at listOnTimeout (node:internal/timers:605:17)
      at process.processTimers (node:internal/timers:541:7)

  3) Promise.all
       should resolve promises to array:
     Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure 
"done()" is called; if returning a Promise, ensure it resolves. 
(/<<PKGBUILDDIR>>/test.js)
      at createTimeoutError (/usr/share/nodejs/mocha/lib/errors.js:386:15)
      at Runnable._timeoutError (/usr/share/nodejs/mocha/lib/runnable.js:431:10)
      at Timeout.<anonymous> (/usr/share/nodejs/mocha/lib/runnable.js:246:24)
      at listOnTimeout (node:internal/timers:605:17)
      at process.processTimers (node:internal/timers:541:7)

  4) unhandledRejection/rejectionHandled events
       should not emit any events if handled before the next turn:
     Uncaught TypeError: util.isDate is not a function
      at _deepEqual (debian/tests/test_modules/core-assert/index.js:173:19)
      at ok.deepEqual (debian/tests/test_modules/core-assert/index.js:153:8)
      at Immediate.<anonymous> (test.js:196:11)
      at process.processImmediate (node:internal/timers:504:21)

  5) unhandledRejection/rejectionHandled events
       should not emit any events when handled by a chained promise:
     Uncaught TypeError: util.isDate is not a function
      at _deepEqual (debian/tests/test_modules/core-assert/index.js:173:19)
      at ok.deepStrictEqual 
(debian/tests/test_modules/core-assert/index.js:159:8)
      at Timeout._onTimeout (test.js:225:11)
      at listOnTimeout (node:internal/timers:605:17)
      at process.processTimers (node:internal/timers:541:7)



dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 5
make: *** [debian/rules:8: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess failed with exit 
status 2
--------------------------------------------------------------------------------

--- End Message ---
--- Begin Message --- 
Source: node-pinkie
Source-Version: 2.0.4-3
Done: Xavier Guimard <[email protected]>

We believe that the bug you reported is fixed in the latest version of
node-pinkie, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Xavier Guimard <[email protected]> (supplier of updated node-pinkie package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Sat, 02 May 2026 08:38:13 +0200
Source: node-pinkie
Architecture: source
Version: 2.0.4-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 
<[email protected]>
Changed-By: Xavier Guimard <[email protected]>
Closes: 1135433
Changes:
 node-pinkie (2.0.4-3) unstable; urgency=medium
 .
   * Team upload
   * Replace removed util.is{Date,RegExp} with instanceof in test core-
     assert (Closes: #1135433)
   * Declare compliance with policy 4.7.4
   * Update debian/watch to version 5
Checksums-Sha1: 
 6e1f362a367ef1a65fa38011c6ae8be5e09fbab3 2074 node-pinkie_2.0.4-3.dsc
 ca7c71edf3dc6e7b3dfee9deea34f83d4bbab702 15844 
node-pinkie_2.0.4-3.debian.tar.xz
Checksums-Sha256: 
 6c059093169bf0cce5d4e1075fdb645a23ff61988f1ceb896a22029d03e3526f 2074 
node-pinkie_2.0.4-3.dsc
 d639e0b667a85a93c3d1a65c4a4ea10147cec77b2c02c7ebb660761c631fb471 15844 
node-pinkie_2.0.4-3.debian.tar.xz
Files: 
 576504f7c3cd993874bf74448fb46655 2074 javascript optional 
node-pinkie_2.0.4-3.dsc
 60a467a448144e1a584e5feada78fd2e 15844 javascript optional 
node-pinkie_2.0.4-3.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmn1nDQACgkQ9tdMp8mZ
7unOPg//aWV1cPwrQ6wxxgPz4WyZMlajekJwIJj13e4MIzS1q4C3S0T3l6gcpJc8
hQwVkWao8nNMcXd0mO1DbyLo/Ru4J343rDzVysyhO7TDKYCjh3U7VebqycBelpVc
6DB21OKzRNZjG/rFOCYqg4yBFykfDaNrS/enUSbcYHO0eVnnL1pZ7A1hCW9BxKxv
WXiPvewoRfRKie3AfXRBxbu2lOPQT/BD4iRL6punRKoNveXNPjjBofQxDU0OGUhR
snW3MesA73ZCKAR0tMdDjAWKgiqT2u7JFlu+cEaphV0Tbl+gVRoofvRBVqXHxNm0
FNQdOdqwftrKtk8Q0Jeqv35RYqjb+J7vz2D6nObgwOvGGmGF05ulann4p40BV1jZ
tF3Lmr7VLkF7Gr+0+lXu2uHvdDWdfjF4UqbqCUggydwuZhLQWYv8+xYnV6LBciWp
yS9AekX7hsXolfvuoLyejSPuA9FxxIzstbvnDfoHov9XaADWp2dSFCUeWv91un02
Xdh5fL0t/JDdwQpgnyrbrmgLewxcszRZa5dEqdySA6dhiyJ9GL6zaszxaWwZYFhp
BjvqDWrOhWEt8MsEFsSgGY7hp0wTnLfj2N3f8qJXCCip1MbpJRHN7kIVHlUlEUXG
9qKv9W8WA0EVthZgk9LIPEwtEChOa7sGlcn4Dv6DiK84hRzVk8M=
=MxDL
-----END PGP SIGNATURE-----

Attachment: pgp1NB4jGCUz3.pgp
Description: PGP signature


--- End Message ---
-- 
Pkg-javascript-devel mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Reply via email to