Your message dated Thu, 12 Feb 2026 13:49:52 +0200
with message-id <aY2-YOzzUBKOQLH5@localhost>
and subject line Re: Bug#1127443: nodejs: FTBFS: make[2]: *** [Makefile:584:
test-ci-js] Error 1
has caused the Debian Bug report #1127443,
regarding nodejs: FTBFS: make[2]: *** [Makefile:584: test-ci-js] Error 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 [email protected]
immediately.)
--
1127443: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1127443
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: nodejs
Version: 22.22.0+dfsg+~cs22.19.6-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: [email protected]
Dear maintainer,
while rebuilding nodejs for the libsimdutf transition, the package
failed to build:
Failed tests:
out/Release/node --test-reporter=./test/common/test-error-reporter.js
--test-reporter-destination=stdout
/tmp/tmp.vV2eizqBkc.nodejs/test/parallel/test-http2-client-set-priority.js
out/Release/node --test-reporter=./test/common/test-error-reporter.js
--test-reporter-destination=stdout
/tmp/tmp.vV2eizqBkc.nodejs/test/parallel/test-http2-client-unescaped-path.js
out/Release/node --test-reporter=./test/common/test-error-reporter.js
--test-reporter-destination=stdout
/tmp/tmp.vV2eizqBkc.nodejs/test/parallel/test-http2-multi-content-length.js
out/Release/node --test-reporter=./test/common/test-error-reporter.js
--test-reporter-destination=stdout
/tmp/tmp.vV2eizqBkc.nodejs/test/parallel/test-http2-priority-event.js
out/Release/node --test-reporter=./test/common/test-error-reporter.js
--test-reporter-destination=stdout
/tmp/tmp.vV2eizqBkc.nodejs/test/parallel/test-http2-reset-flood.js
out/Release/node --test-reporter=./test/common/test-error-reporter.js
--test-reporter-destination=stdout
/tmp/tmp.vV2eizqBkc.nodejs/test/parallel/test-http2-max-invalid-frames.js
out/Release/node --test-reporter=./test/common/test-error-reporter.js
--test-reporter-destination=stdout
/tmp/tmp.vV2eizqBkc.nodejs/test/parallel/test-http2-misbehaving-flow-control.js
out/Release/node --test-reporter=./test/common/test-error-reporter.js
--test-reporter-destination=stdout
/tmp/tmp.vV2eizqBkc.nodejs/test/parallel/test-http2-misbehaving-flow-control-paused.js
make[2]: *** [Makefile:584: test-ci-js] Error 1
make[2]: Leaving directory '/tmp/tmp.vV2eizqBkc.nodejs'
See
https://buildd.debian.org/status/fetch.php?pkg=nodejs&arch=amd64&ver=22.22.0%2Bdfsg%2B%7Ecs22.19.6-1%2Bb2&stamp=1770553772&raw=0
for details.
Cheers
--
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Version: 24.13.0+dfsg+~cs24.10.7-2
On Sun, Feb 08, 2026 at 10:31:58PM +0100, Jérémy Lal wrote:
> Le dim. 8 févr. 2026 à 22:29, Sebastian Ramacher <[email protected]> a
> écrit :
>
> > Source: nodejs
> > Version: 22.22.0+dfsg+~cs22.19.6-1
> > Severity: serious
> > Tags: ftbfs
> > Justification: fails to build from source (but built successfully in the
> > past)
> > X-Debbugs-Cc: [email protected]
> >
> > Dear maintainer,
> >
> > while rebuilding nodejs for the libsimdutf transition, the package
> > failed to build:
> >
> > Failed tests:
> > out/Release/node --test-reporter=./test/common/test-error-reporter.js
> > --test-reporter-destination=stdout
> > /tmp/tmp.vV2eizqBkc.nodejs/test/parallel/test-http2-client-set-priority.js
> > out/Release/node --test-reporter=./test/common/test-error-reporter.js
> > --test-reporter-destination=stdout
> > /tmp/tmp.vV2eizqBkc.nodejs/test/parallel/test-http2-client-unescaped-path.js
> > out/Release/node --test-reporter=./test/common/test-error-reporter.js
> > --test-reporter-destination=stdout
> > /tmp/tmp.vV2eizqBkc.nodejs/test/parallel/test-http2-multi-content-length.js
> > out/Release/node --test-reporter=./test/common/test-error-reporter.js
> > --test-reporter-destination=stdout
> > /tmp/tmp.vV2eizqBkc.nodejs/test/parallel/test-http2-priority-event.js
> > out/Release/node --test-reporter=./test/common/test-error-reporter.js
> > --test-reporter-destination=stdout
> > /tmp/tmp.vV2eizqBkc.nodejs/test/parallel/test-http2-reset-flood.js
> > out/Release/node --test-reporter=./test/common/test-error-reporter.js
> > --test-reporter-destination=stdout
> > /tmp/tmp.vV2eizqBkc.nodejs/test/parallel/test-http2-max-invalid-frames.js
> > out/Release/node --test-reporter=./test/common/test-error-reporter.js
> > --test-reporter-destination=stdout
> > /tmp/tmp.vV2eizqBkc.nodejs/test/parallel/test-http2-misbehaving-flow-control.js
> > out/Release/node --test-reporter=./test/common/test-error-reporter.js
> > --test-reporter-destination=stdout
> > /tmp/tmp.vV2eizqBkc.nodejs/test/parallel/test-http2-misbehaving-flow-control-paused.js
> > make[2]: *** [Makefile:584: test-ci-js] Error 1
> > make[2]: Leaving directory '/tmp/tmp.vV2eizqBkc.nodejs'
> >
> >
> Thank you,
>
> this is more likely to be caused by nghttp2 1.68.0-1
>...
Yes, this seems to be (untested):
https://nghttp2.org/blog/2025/03/02/nghttp2-v1-65-0/
https://github.com/nodejs/node/commit/0b987e57414f698a0cf109a53f6aaa26c23a9a93
This commit is already included in the version in experimental and that
version still builds, closing the bug there.
cu
Adrian
--- End Message ---
