Joyee Cheung 3fa5d80eda benchmark: chunky http client should exit with 0 ...

Previously when there is an error in the chunky client of the
http benchmark, the server would not check the exit code and
thus produce invalid results.

PR-URL: https://github.com/nodejs/node/pull/12916
Fixes: https://github.com/nodejs/node/issues/12903
Reviewed-By: Vse Mozhet Byt <vsemozhetbyt@gmail.com>
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>

2017-05-13 23:30:29 +08:00

..

_chunky_http_client.js

benchmark: update an obsolete path

2017-05-08 23:19:41 +03:00

bench-parser.js

benchmark: control HTTP benchmarks run time

2017-04-09 18:16:08 +08:00

check_invalid_header_char.js

http: optimize checkInvalidHeaderChar()

2016-06-14 15:13:00 -04:00

check_is_http_token.js

benchmark: increase http token check iterations

2016-06-14 15:13:00 -04:00

chunked.js

benchmark: control HTTP benchmarks run time

2017-04-09 18:16:08 +08:00

client-request-body.js

benchmark: control HTTP benchmarks run time

2017-04-09 18:16:08 +08:00

cluster.js

benchmark: reduce string concatenations

2017-04-20 04:46:37 +03:00

create-clientrequest.js

benchmark: control HTTP benchmarks run time

2017-04-09 18:16:08 +08:00

end-vs-write-end.js

benchmark: control HTTP benchmarks run time

2017-04-09 18:16:08 +08:00

http_server_for_chunky_client.js

benchmark: chunky http client should exit with 0

2017-05-13 23:30:29 +08:00

simple.js

benchmark: reduce string concatenations

2017-04-20 04:46:37 +03:00