You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I can reproduce this locally, and get errors even on Node 8; so it’s most likely a bug in the test.
It also looks like increasing the timer duration in the test helps. Ideally, we’d just get rid of it, and instead call res.end() based on other events happening?
@addaleax I tried that approach, but couldn't get the dump to happen reliably. It would be good if someone else brought in some new eyes into the problem. That part of the codebase was never tested :/.
not ok 732 parallel/test-http-dump-req-when-res-ends --- duration_ms: 1.242 severity: fail stack: |- resume called Mismatched <anonymous> function calls. Expected at least 1, actual 0. at Object.exports.mustCallAtLeast (/usr/home/iojs/build/workspace/node-test-commit-freebsd/nodes/freebsd10-64/test/common/index.js:431:10) at IncomingMessage.<anonymous> (/usr/home/iojs/build/workspace/node-test-commit-freebsd/nodes/freebsd10-64/test/parallel/test-http-dump-req-when-res-ends.js:12:27) at IncomingMessage.<anonymous> (/usr/home/iojs/build/workspace/node-test-commit-freebsd/nodes/freebsd10-64/test/common/index.js:467:15) at IncomingMessage.emit (events.js:182:13) at resume_ (_stream_readable.js:855:10) at process._tickCallback (internal/process/next_tick.js:174:19)
$ tools/test.py -j 96 --repeat 192 test/parallel/test-http-dump-req-when-res-ends.js === release test-http-dump-req-when-res-ends === Path: parallel/test-http-dump-req-when-res-endsresume calledMismatched <anonymous> function calls. Expected at least 1, actual 0. at Object.exports.mustCallAtLeast (/Users/trott/io.js/test/common/index.js:431:10) at IncomingMessage.<anonymous> (/Users/trott/io.js/test/parallel/test-http-dump-req-when-res-ends.js:12:27) at IncomingMessage.<anonymous> (/Users/trott/io.js/test/common/index.js:467:15) at IncomingMessage.emit (events.js:182:13) at resume_ (_stream_readable.js:855:10) at process._tickCallback (internal/process/next_tick.js:174:19)Command: out/Release/node /Users/trott/io.js/test/parallel/test-http-dump-req-when-res-ends.js=== release test-http-dump-req-when-res-ends === Path: parallel/test-http-dump-req-when-res-endsresume calledMismatched <anonymous> function calls. Expected at least 1, actual 0. at Object.exports.mustCallAtLeast (/Users/trott/io.js/test/common/index.js:431:10) at IncomingMessage.<anonymous> (/Users/trott/io.js/test/parallel/test-http-dump-req-when-res-ends.js:12:27) at IncomingMessage.<anonymous> (/Users/trott/io.js/test/common/index.js:467:15) at IncomingMessage.emit (events.js:182:13) at resume_ (_stream_readable.js:855:10) at process._tickCallback (internal/process/next_tick.js:174:19)Command: out/Release/node /Users/trott/io.js/test/parallel/test-http-dump-req-when-res-ends.js[SNIP]
Activity
addaleax commentedon Mar 5, 2018
I can reproduce this locally, and get errors even on Node 8; so it’s most likely a bug in the test.
It also looks like increasing the timer duration in the test helps. Ideally, we’d just get rid of it, and instead call
res.end()based on other events happening?mcollina commentedon Mar 5, 2018
@addaleax I tried that approach, but couldn't get the dump to happen reliably. It would be good if someone else brought in some new eyes into the problem. That part of the codebase was never tested :/.
Trott commentedon Apr 5, 2018
Happened on FreeBSD today:
https://ci.nodejs.org/job/node-test-commit-freebsd/16727/nodes=freebsd10-64/console
Trott commentedon Apr 5, 2018
Very easy to reproduce:
Trott commentedon Apr 5, 2018
Opening PR to move to sequential. That's more of a mitigation strategy than a fix, but it's better than doing nothing.
Trott commentedon Apr 5, 2018
PR: #19819
test: move test-http-dump-req-when-res-end
test: move test-http-dump-req-when-res-end
test,http: fix http dump test
test,http: fix http dump test