Package: src:node-multiparty
Version: 4.2.2-2
Severity: serious
Control: close -1 4.2.3-2
Tags: ftbfs bullseye

Dear maintainer:

During a rebuild of all packages in bullseye, your package failed to build:

--------------------------------------------------------------------------------
[...]
 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/multiparty
        /bin/sh -ex debian/tests/pkg-js/test
+ mocha --bail --check-leaks test/


  multiparty
    fixture tests
      content-type
        ✓ charset
        ✓ charset-last
        ✓ custom
        ✓ custom-equal-sign
      encoding
        ✓ menu_seperator.png
        ✓ beta-sticker-1.png
        ✓ blank.gif
        ✓ binaryfile.tar.gz
        ✓ plain.txt
      filename
        1) empty


  9 passing (2s)
  1 failing

  1) multiparty
       fixture tests
         filename
           empty:
     Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure "done()" is 
called; if returning a Promise, ensure it resolves. (/<<PKGBUILDDIR>>/test/test.js)
      at Test.Runnable._timeoutError 
(/usr/share/nodejs/mocha/lib/runnable.js:432:10)
      at Timeout.<anonymous> (/usr/share/nodejs/mocha/lib/runnable.js:244:24)
      at listOnTimeout (internal/timers.js:554:17)
      at processTimers (internal/timers.js:497:7)



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

The above is just how the build ends and not necessarily the most relevant part.
If required, the full build log is available here:

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

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

If you could not 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 affects, so that this is still visible in the BTS web
page for this package.

Thanks.

Reply via email to