[Pkg-javascript-devel] Bug#1078894: node-resolve: FTBFS: test/index.js wasi not supported; requiring throws
Santiago Vila
sanvila at debian.org
Sat Aug 17 14:40:25 BST 2024
Package: src:node-resolve
Version: 1.22.1+~cs5.31.10-1
Severity: serious
Control: close -1 1.22.8+~cs5.34.15-2
Tags: ftbfs bookworm
Dear maintainer:
During a rebuild of all packages in bookworm, your package failed to build:
--------------------------------------------------------------------------------
[...]
debian/rules binary
dh binary
dh_update_autotools_config
dh_autoreconf
dh_auto_configure --buildsystem=nodejs
Link node_modules/is-core-module -> ../is-core-module
Link node_modules/object-keys -> ../object-keys
Link node_modules/path-parse -> ../path-parse
Link node_modules/@types/resolve -> ../../types-resolve
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
[... snipped ...]
✓ requiring node:url does not throw
✓ util is a core module
✓ requiring util does not throw
✓ requiring node:util does not throw
✓ util/types is a core module
✓ requiring util/types does not throw
✓ requiring node:util/types does not throw
✓ v8 is a core module
✓ requiring v8 does not throw
✓ requiring node:v8 does not throw
✓ vm is a core module
✓ requiring vm does not throw
✓ requiring node:vm does not throw
✓ wasi is a core module
✓ requiring wasi does not throw
✓ requiring node:wasi does not throw
✓ worker_threads is a core module
✓ requiring worker_threads does not throw
✓ requiring node:worker_threads does not throw
✓ zlib is a core module
✓ requiring zlib does not throw
✓ requiring node:zlib does not throw
✓ _http_agent is a core module
✓ requiring _http_agent does not throw
✓ requiring node:_http_agent does not throw
✓ _http_client is a core module
✓ requiring _http_client does not throw
✓ requiring node:_http_client does not throw
✓ _http_common is a core module
✓ requiring _http_common does not throw
✓ requiring node:_http_common does not throw
✓ _http_incoming is a core module
✓ requiring _http_incoming does not throw
✓ requiring node:_http_incoming does not throw
✓ _http_outgoing is a core module
✓ requiring _http_outgoing does not throw
✓ requiring node:_http_outgoing does not throw
✓ _http_server is a core module
✓ requiring _http_server does not throw
✓ requiring node:_http_server does not throw
✓ _stream_duplex is a core module
✓ requiring _stream_duplex does not throw
✓ requiring node:_stream_duplex does not throw
✓ _stream_passthrough is a core module
✓ requiring _stream_passthrough does not throw
✓ requiring node:_stream_passthrough does not throw
✓ _stream_readable is a core module
✓ requiring _stream_readable does not throw
✓ requiring node:_stream_readable does not throw
✓ _stream_transform is a core module
✓ requiring _stream_transform does not throw
✓ requiring node:_stream_transform does not throw
✓ _stream_wrap is a core module
✓ requiring _stream_wrap does not throw
✓ requiring node:_stream_wrap does not throw
✓ _stream_writable is a core module
✓ requiring _stream_writable does not throw
✓ requiring node:_stream_writable does not throw
✓ _tls_common is a core module
✓ requiring _tls_common does not throw
✓ requiring node:_tls_common does not throw
✓ _tls_wrap is a core module
✓ requiring _tls_wrap does not throw
✓ requiring node:_tls_wrap does not throw
✓ assert is a core module
✓ requiring assert does not throw
✓ requiring node:assert does not throw
✓ assert/strict is a core module
✓ requiring assert/strict does not throw
✓ requiring node:assert/strict does not throw
✓ async_hooks is a core module
✓ requiring async_hooks does not throw
✓ requiring node:async_hooks does not throw
✓ buffer is a core module
✓ requiring buffer does not throw
✓ requiring node:buffer does not throw
✓ child_process is a core module
✓ requiring child_process does not throw
✓ requiring node:child_process does not throw
✓ cluster is a core module
✓ requiring cluster does not throw
✓ requiring node:cluster does not throw
✓ console is a core module
✓ requiring console does not throw
✓ requiring node:console does not throw
✓ constants is a core module
✓ requiring constants does not throw
✓ requiring node:constants does not throw
✓ crypto is a core module
✓ requiring crypto does not throw
✓ requiring node:crypto does not throw
✓ dgram is a core module
✓ requiring dgram does not throw
✓ requiring node:dgram does not throw
✓ diagnostics_channel is a core module
✓ requiring diagnostics_channel does not throw
✓ requiring node:diagnostics_channel does not throw
✓ dns is a core module
✓ requiring dns does not throw
✓ requiring node:dns does not throw
✓ dns/promises is a core module
✓ requiring dns/promises does not throw
✓ requiring node:dns/promises does not throw
✓ domain is a core module
✓ requiring domain does not throw
✓ requiring node:domain does not throw
✓ events is a core module
✓ requiring events does not throw
✓ requiring node:events does not throw
✓ fs is a core module
✓ requiring fs does not throw
✓ requiring node:fs does not throw
✓ fs/promises is a core module
✓ requiring fs/promises does not throw
✓ requiring node:fs/promises does not throw
✓ http is a core module
✓ requiring http does not throw
✓ requiring node:http does not throw
✓ http2 is a core module
✓ requiring http2 does not throw
✓ requiring node:http2 does not throw
✓ https is a core module
✓ requiring https does not throw
✓ requiring node:https does not throw
✓ inspector is a core module
✓ requiring inspector does not throw
✓ requiring node:inspector does not throw
✓ module is a core module
✓ requiring module does not throw
✓ requiring node:module does not throw
✓ net is a core module
✓ requiring net does not throw
✓ requiring node:net does not throw
✓ os is a core module
✓ requiring os does not throw
✓ requiring node:os does not throw
✓ path is a core module
✓ requiring path does not throw
✓ requiring node:path does not throw
✓ path/posix is a core module
✓ requiring path/posix does not throw
✓ requiring node:path/posix does not throw
✓ path/win32 is a core module
✓ requiring path/win32 does not throw
✓ requiring node:path/win32 does not throw
✓ perf_hooks is a core module
✓ requiring perf_hooks does not throw
✓ requiring node:perf_hooks does not throw
✓ process is a core module
✓ requiring process does not throw
✓ requiring node:process does not throw
✓ punycode is a core module
✓ requiring punycode does not throw
✓ requiring node:punycode does not throw
✓ querystring is a core module
✓ requiring querystring does not throw
✓ requiring node:querystring does not throw
✓ readline is a core module
✓ requiring readline does not throw
✓ requiring node:readline does not throw
✓ readline/promises is a core module
✓ requiring readline/promises does not throw
✓ requiring node:readline/promises does not throw
✓ repl is a core module
✓ requiring repl does not throw
✓ requiring node:repl does not throw
✓ stream is a core module
✓ requiring stream does not throw
✓ requiring node:stream does not throw
✓ stream/consumers is a core module
✓ requiring stream/consumers does not throw
✓ requiring node:stream/consumers does not throw
✓ stream/promises is a core module
✓ requiring stream/promises does not throw
✓ requiring node:stream/promises does not throw
✓ stream/web is a core module
✓ requiring stream/web does not throw
✓ requiring node:stream/web does not throw
✓ string_decoder is a core module
✓ requiring string_decoder does not throw
✓ requiring node:string_decoder does not throw
✓ sys is a core module
✓ requiring sys does not throw
✓ requiring node:sys does not throw
✓ timers is a core module
✓ requiring timers does not throw
✓ requiring node:timers does not throw
✓ timers/promises is a core module
✓ requiring timers/promises does not throw
✓ requiring node:timers/promises does not throw
✓ tls is a core module
✓ requiring tls does not throw
✓ requiring node:tls does not throw
✓ trace_events is a core module
✓ requiring trace_events does not throw
✓ requiring node:trace_events does not throw
✓ tty is a core module
✓ requiring tty does not throw
✓ requiring node:tty does not throw
✓ url is a core module
✓ requiring url does not throw
✓ requiring node:url does not throw
✓ util is a core module
✓ requiring util does not throw
✓ requiring node:util does not throw
✓ util/types is a core module
✓ requiring util/types does not throw
✓ requiring node:util/types does not throw
✓ v8 is a core module
✓ requiring v8 does not throw
✓ requiring node:v8 does not throw
✓ vm is a core module
✓ requiring vm does not throw
✓ requiring node:vm does not throw
✓ wasi is a core module
✓ requiring wasi does not throw
✓ requiring node:wasi does not throw
✓ worker_threads is a core module
✓ requiring worker_threads does not throw
✓ requiring node:worker_threads does not throw
✓ zlib is a core module
✓ requiring zlib does not throw
✓ requiring node:zlib does not throw
✓ node:test is a core module
✓ requiring node:test does not throw
✓ fs is a core module even if Object.prototype lies
✓ path is a core module even if Object.prototype lies
✓ path is a core module even if Object.prototype matches data
✓ "not a core module" is not a core module even if Object.prototype lies
522 passing (399.392ms)
1 failing
1) test/index.js wasi not supported; requiring throws:
Error: wasi not supported; requiring throws
at Error: wasi not supported; requiring throws
at at Test.assert [as _assert] (/usr/share/nodejs/tape/lib/test.js:312:48)
at at Test.bound [as _assert] (/usr/share/nodejs/tape/lib/test.js:95:17)
at at Test.throws (/usr/share/nodejs/tape/lib/test.js:677:7)
at at Test.bound [as throws] (/usr/share/nodejs/tape/lib/test.js:95:17)
at at Test.<anonymous> (test/index.js:37:17)
at at Test.bound [as _cb] (/usr/share/nodejs/tape/lib/test.js:95:17)
at at Test.run (/usr/share/nodejs/tape/lib/test.js:115:28)
at at Test.bound [as run] (/usr/share/nodejs/tape/lib/test.js:95:17)
at at Test._end (/usr/share/nodejs/tape/lib/test.js:218:5)
at at Test.bound [as _end] (/usr/share/nodejs/tape/lib/test.js:95:17)
make[1]: *** [debian/rules:46: test_component_packages] Error 1
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
make: *** [debian/rules:7: binary] Error 2
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/bookworm/
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.
More information about the Pkg-javascript-devel
mailing list