From 9d1bfd92d9a6a339e9695ed29ad1ddd26374eaa6 Mon Sep 17 00:00:00 2001 From: Bartosz Sosnowski Date: Tue, 31 May 2016 18:25:15 +0200 Subject: [PATCH] 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. --- benchmark/child_process/child-process-exec-stdout.js | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/benchmark/child_process/child-process-exec-stdout.js b/benchmark/child_process/child-process-exec-stdout.js index 79efb6fadf2aeb..6194f66b55d987 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] });