From 5386b23f641b9bddc3a8dd93f85e43f987011d02 Mon Sep 17 00:00:00 2001 From: Bartosz Sosnowski Date: Tue, 31 May 2016 18:25:15 +0200 Subject: benchmark: fix child-process-exec-stdout on win This benchmark fails on Windows when trying to execute command which is more than 32k in size. This commits skips this one case when running under Windows. PR-URL: https://github.com/nodejs/node/pull/7178 Reviewed-By: Trott - Rich Trott Reviewed-By: orangemocha - Alexis Campailla --- benchmark/child_process/child-process-exec-stdout.js | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) (limited to 'benchmark/child_process') diff --git a/benchmark/child_process/child-process-exec-stdout.js b/benchmark/child_process/child-process-exec-stdout.js index 79efb6fadf2..6194f66b55d 100644 --- a/benchmark/child_process/child-process-exec-stdout.js +++ b/benchmark/child_process/child-process-exec-stdout.js @@ -1,7 +1,12 @@ 'use strict'; const common = require('../common.js'); + +var messagesLength = [64, 256, 1024, 4096]; +// Windows does not support that long arguments +if (process.platform !== 'win32') + messagesLength.push(32768); const bench = common.createBenchmark(main, { - len: [64, 256, 1024, 4096, 32768], + len: messagesLength, dur: [5] }); -- cgit v1.2.3