Source: node-timed-out Version: 4.0.1-1 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org
Dear Maintainer, node-timed-out fails to build from source in unstable/amd64. Not sure why it fails to timeout when accessing http://192.0.2.1 but this seems to be a broken way of testing anyway... […] 1) should emit ETIMEDOUT when connection timeout expires when connection is established ✓ should emit ESOCKETTIMEDOUT (no data) (221ms) ✓ should emit ESOCKETTIMEDOUT (only first chunk of body) (313ms) ✓ should be able to only apply connect timeout ✓ should be able to only apply socket timeout (55ms) ✓ should not add event handlers twice for the same socket ✓ should set socket timeout if socket is already connected (211ms) ✓ should clear socket timeout for keep-alive sockets 7 passing (3s) 1 failing 1) should emit ETIMEDOUT when connection timeout expires: Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. at Timeout.<anonymous> (/usr/lib/nodejs/mocha/lib/runnable.js:238:19) debian/rules:13: recipe for target 'override_dh_auto_test' failed make[1]: *** [override_dh_auto_test] Error 1 […] The full build log is attached or can be viewed here: https://tests.reproducible-builds.org/debian/logs/unstable/amd64/node-timed-out_4.0.1-1.build1.log.gz Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
node-timed-out.4.0.1-1.unstable.amd64.log.txt.gz
Description: Binary data
