[Pkg-javascript-devel] Bug#1135424: node-follow-redirects: FTBFS: Error: Timeout of 2000ms exceeded.
Santiago Vila
sanvila at debian.org
Sat May 2 00:13:18 BST 2026
Package: src:node-follow-redirects
Version: 1.16.0+~1.14.4-1
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-follow-redirects, 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 -rf types-follow-redirects/node_modules/.cache types-follow-redirects/.nyc_output
rm ./node_modules/.cache
rm types-follow-redirects/node_modules/.cache
rm ./node_modules/.cache
unlink node_modules/@types/follow-redirects
dh_clean
debian/rules binary
dh binary
dh_update_autotools_config
dh_autoreconf
dh_auto_configure --buildsystem=nodejs
Link node_modules/@types/follow-redirects -> ../../types-follow-redirects
dh_auto_build --buildsystem=nodejs
No build command found, searching known files
No build command found, searching known files
dh_auto_test --buildsystem=nodejs
ln -s ../. node_modules/follow-redirects
/bin/sh -ex debian/tests/pkg-js/test
+ mocha --exit --invert --grep deduplicated
follow-redirects
â http.get with string and callback - redirect
â http.get with URL object and callback - redirect
â http.get with options object and callback - redirect
â http.get with string and callback - no redirect
â http.get with options object and callback - no redirect
â http.get with host option and callback - redirect
â http.get to IPv4 address
â http.get to IPv6 address
â http.get to bracketed IPv4 address
â http.get to bracketed IPv4 address specified as host
â http.get to bracketed IPv4 address specified as hostname
â http.get to bracketed hostname
â http.get redirecting to IPv4 address
â http.get redirecting to IPv6 address
â http.get redirecting to bracketed IPv4 address
â http.get redirecting to bracketed hostname
â http.get with response event
â http.get with relative URL path
â redirect to URL with fragment
â should return with the original status code if the response does not contain a location header
â should emit connection errors on the returned stream
â should emit socket events on the returned stream
â should emit connect events on the returned stream
â emits an error on redirects with an invalid location
â emits an error when the request fails for another reason
(node:53) [DEP0169] DeprecationWarning: `url.parse()` behavior is not standardized and prone to errors that have security implications. Use the WHATWG URL API instead. CVEs are not issued for `url.parse()` vulnerabilities.
(Use `node --trace-deprecation ...` to show where the warning was created)
â should follow redirects over https
â should destroy responses
â should honor query params in redirects
â should allow aborting
â should provide connection
â should provide flushHeaders
â should provide getHeader
â should provide removeHeader
â should provide setHeader
â should provide setNoDelay
â should provide setSocketKeepAlive
â should provide setTimeout
â should provide socket
â should wait for an explicit call to end
â errors on write after end
â should support writing into request stream without redirects
â should support writing into request stream with redirects
â should support piping into request stream without redirects
â should support piping into request stream with redirects
â should support piping into request stream with explicit Content-Length without redirects
â should support piping into request stream with explicit Content-Length with redirects
â keeps the header when redirected from HTTP to HTTPS
â drops the header when redirected from HTTPS to HTTP
â keeps the header when redirected from HTTP to HTTPS
â drops the header when redirected from HTTPS to HTTP
â keeps the header when redirected from HTTP to HTTPS
â drops the header when redirected from HTTPS to HTTP
â keeps the header when redirected from HTTP to HTTPS
â drops the header when redirected from HTTPS to HTTP
â keeps the header when redirected from HTTP to HTTPS
â drops the header when redirected from HTTPS to HTTP
â keeps the header when redirected from HTTP to HTTPS
â drops the header when redirected from HTTPS to HTTP
â keeps the header when redirected from HTTP to HTTPS
â drops the header when redirected from HTTPS to HTTP
â keeps the header when redirected from HTTP to HTTPS
â drops the header when redirected from HTTPS to HTTP
setTimeout
â clears timeouts after a successful response
â clears timeouts after an error response
â handles errors occuring before a socket is established
â sets a timeout when the socket already exists
â destroys the socket after configured inactivity period (102ms)
â should timeout on the final request
â should include redirect delays in the timeout
â overrides existing timeouts
should obey a `maxRedirects` property
â which defaults to 21 (39ms)
â which can be set globally
â set as an option on an individual request
the trackRedirects option
when not set
â should not track redirects
when set to true
â should track redirects
should switch to safe methods when appropriate
when redirecting with status code 300
â should reuse GET
â should reuse HEAD
â should reuse POST
â should reuse PUT
â should reuse DELETE
when redirecting with status code 301
â should reuse GET
â should reuse HEAD
â should switch from POST to GET
â should reuse PUT
â should reuse DELETE
when redirecting with status code 302
â should reuse GET
â should reuse HEAD
â should switch from POST to GET
â should reuse PUT
â should reuse DELETE
when redirecting with status code 303
â should reuse GET
â should reuse HEAD
â should switch from POST to GET
â should switch from PUT to GET
â should switch from DELETE to GET
when redirecting with status code 307
â should reuse GET
â should reuse HEAD
â should reuse POST
â should reuse PUT
â should reuse DELETE
should handle cross protocol redirects
â (https -> http -> https)
â (http -> https -> http)
should error on an unsupported protocol redirect
â (http -> about)
should obey a `maxBodyLength` property
â which defaults to 10MB
â set globally, on write
1) "after each" hook for "set globally, on write"
105 passing (2s)
1 failing
1) follow-redirects
"after each" hook for "set globally, on write":
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 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)
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 failed with exit status 2
--------------------------------------------------------------------------------
More information about the Pkg-javascript-devel
mailing list