Your message dated Thu, 21 Jan 2021 05:18:22 +0000
with message-id <e1l2smq-0000l2...@fasolo.debian.org>
and subject line Bug#980648: fixed in node-execa 4.1.0+dfsg+~cs19.3.6-5
has caused the Debian Bug report #980648,
regarding node-execa: FTBFS: dh_auto_test: error: cd ./human-signals && sh -ex 
../debian/nodejs/human-signals/test returned exit code 1
to be marked as done.

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

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
980648: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980648
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-execa
Version: 4.1.0+dfsg+~cs19.3.6-4
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210120 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> echo 'int main() { return 0; }' | gcc -x c -o test/fixtures/fast-exit-linux -
> dh_auto_build --buildsystem=nodejs
> No build command found, searching known files
> Found debian/nodejs/human-signals/build
>       cd ./human-signals && sh -ex ../debian/nodejs/human-signals/build
> + babeljs -d build/src --presets=@babel/preset-env src/
> Successfully compiled 4 files with Babel (685ms).
> 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
> make[1]: Leaving directory '/<<PKGBUILDDIR>>'
>    dh_auto_test --buildsystem=nodejs
>       ln -s ../debian/tests/test_modules/test-each node_modules/test-each
>       ln -s ../debian/tests/test_modules/big-cartesian 
> node_modules/big-cartesian
>       ln -s ../. node_modules/execa
>       cd ./human-signals && sh -ex ../debian/nodejs/human-signals/test
> + jest --ci --testRegex test/main.js
> FAIL test/main.js
>   ● Test suite failed to run
> 
>     Cannot find module 'ajv' from 'test/main.js'
> 
>       235 | 
>       236 |     const relativePath = (0, 
> _slash().default)(path().relative(this._options.rootDir, from)) || '.';
>     > 237 |     throw new _ModuleNotFoundError.default(`Cannot find module 
> '${moduleName}' from '${relativePath}'`, moduleName);
>           |           ^
>       238 |   }
>       239 | 
>       240 |   _isAliasModule(moduleName) {
> 
>       at Resolver.resolveModule 
> (../../../../usr/share/nodejs/jest-resolve/build/index.js:237:11)
>       at Object.<anonymous> (test/main.js:4:1)
> 
> Test Suites: 1 failed, 1 total
> Tests:       0 total
> Snapshots:   0 total
> Time:        1.746 s
> Ran all test suites.
> dh_auto_test: error: cd ./human-signals && sh -ex 
> ../debian/nodejs/human-signals/test returned exit code 1

The full build log is available from:
   
http://qa-logs.debian.net/2021/01/20/node-execa_4.1.0+dfsg+~cs19.3.6-4_unstable.log

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 me
so that we can identify if something relevant changed in the meantime.

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

--- End Message ---
--- Begin Message ---
Source: node-execa
Source-Version: 4.1.0+dfsg+~cs19.3.6-5
Done: Xavier Guimard <y...@debian.org>

We believe that the bug you reported is fixed in the latest version of
node-execa, 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 980...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Xavier Guimard <y...@debian.org> (supplier of updated node-execa package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


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

Format: 1.8
Date: Thu, 21 Jan 2021 06:01:35 +0100
Source: node-execa
Architecture: source
Version: 4.1.0+dfsg+~cs19.3.6-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 
<pkg-javascript-de...@lists.alioth.debian.org>
Changed-By: Xavier Guimard <y...@debian.org>
Closes: 980648
Changes:
 node-execa (4.1.0+dfsg+~cs19.3.6-5) unstable; urgency=medium
 .
   * Team upload
   * Add missing test dependency to node-ajv (Closes: #980648)
Checksums-Sha1: 
 1359e0941379aa5da19c3d2c239f737561313a87 4020 
node-execa_4.1.0+dfsg+~cs19.3.6-5.dsc
 a1ee5a6a63e86fab0f03c33317cad520b75e2d5a 8912 
node-execa_4.1.0+dfsg+~cs19.3.6-5.debian.tar.xz
Checksums-Sha256: 
 4136c530caecbe3de0c494e22f5b3d5a2f45c55e56e6e1d9a40788d282e3a308 4020 
node-execa_4.1.0+dfsg+~cs19.3.6-5.dsc
 f7e65333e4beee285ce53c4a25ea07c063a2c78051c720a8c7a456b474fa50d2 8912 
node-execa_4.1.0+dfsg+~cs19.3.6-5.debian.tar.xz
Files: 
 505659f702d947040f04eba41873172f 4020 javascript optional 
node-execa_4.1.0+dfsg+~cs19.3.6-5.dsc
 6f099ef207584fe43f48386e8fd7cb11 8912 javascript optional 
node-execa_4.1.0+dfsg+~cs19.3.6-5.debian.tar.xz

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

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmAJDCwACgkQ9tdMp8mZ
7umhKQ/+Puh5AcZeruVzCsLDKPeU2Vy9WnTuG1Dk8rpYrzP1iHfuVj60rYUKI9T9
gjPkyT06Nxum5gRecbh2ZolwKrt/LMFzbMHXrj5A7aWHl5LodwjS34/It8DZBoek
U+7tJA8MJazri1PIRim956SOn57JxSfQKzC+wjLx/b1pkzIvNzg5YxQZcjBwQ6PM
f4SBN9XrH5BB+MY2zTlBoPsQMl7OZktVVo3gv6XqHJK7+ECj6Whjo6+6IsMDa30S
8UqR0j6n3jtrKlrDs2KCMQgFgOIwS59SS5A6b0F4TKwO53eR7OdhGGbCILCy7/45
uE3TW+6a0Rb6Q1qWGMBZn+v6o3JuIAfIpDy90BelK8zWJoliWiRgPyAeIH9x7CiV
9B7e28xLk4v5cP7pr0q8xg3BL4cK0xov2qjxpjByuaRAcNVi+eucqNrlsPeH4gwY
iadhmzZltZfOsb6J+nM2+sOrAR9KjUWbfFaIq0RmCiQwFlJBiaFypXxKdHOzvXnx
cz8cCa0N2X4DDnx5HXN0YXSczwg+gzcuY2xxVPoXj3Pc6M9Bg6eZZ+4HuR1RkmsA
KPg6a5aidq4IsY6KnF2wj0MfOtN/QalPs7qiNXhxgcl+QVy8z/xo+oPPAgdu6A+d
6ES8jnUTp2zzbld6C3QMQJ0nmeSqPPAGlo1c7EORn8kFHI91Lbw=
=c0Kq
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to