Andreas Madsen 8bb59fdb12 benchmark: missing process.exit after bench.end ... Previously bench.end would call process.exit(0) however this is rather confusing and indeed a few benchmarks had code that assumed otherwise. This adds process.exit(0) to the benchmarks that needs it. PR-URL: https://github.com/nodejs/node/pull/7094 Reviewed-By: Trevor Norris <trev.norris@gmail.com> Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com> Reviewed-By: Brian White <mscdex@mscdex.net> Reviewed-By: Anna Henningsen <anna@addaleax.net>		2016-07-26 13:21:50 +02:00
..
net-c2s-cork.js	benchmark: missing process.exit after bench.end	2016-07-26 13:21:50 +02:00
net-c2s.js	benchmark: missing process.exit after bench.end	2016-07-26 13:21:50 +02:00
net-pipe.js	benchmark: missing process.exit after bench.end	2016-07-26 13:21:50 +02:00
net-s2c.js	benchmark: missing process.exit after bench.end	2016-07-26 13:21:50 +02:00
punycode.js	net: use icu's punycode implementation	2016-06-29 17:10:53 -07:00
tcp-raw-c2s.js	benchmark: missing process.exit after bench.end	2016-07-26 13:21:50 +02:00
tcp-raw-pipe.js	benchmark: missing process.exit after bench.end	2016-07-26 13:21:50 +02:00
tcp-raw-s2c.js	benchmark: missing process.exit after bench.end	2016-07-26 13:21:50 +02:00