From 644bfe14a6976b812b6fc4cc1307e0a9fe1dcb52 Mon Sep 17 00:00:00 2001 From: Santiago Gimeno Date: Sun, 29 May 2016 12:57:58 +0200 Subject: [PATCH] test: fix test-debug-port-numbers on OS X According to kill(2), kill returns `EPERM` error if when signalling a process group any of the members could not be signalled. PR-URL: https://github.com/nodejs/node/pull/7046 Reviewed-By: Colin Ihrig Reviewed-By: Ben Noordhuis --- test/parallel/test-debug-port-numbers.js | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/test/parallel/test-debug-port-numbers.js b/test/parallel/test-debug-port-numbers.js index c7bf1da5f64849..33cdf6035b449a 100644 --- a/test/parallel/test-debug-port-numbers.js +++ b/test/parallel/test-debug-port-numbers.js @@ -44,7 +44,9 @@ function kill(child) { try { process.kill(-child.pid); // Kill process group. } catch (e) { - assert.strictEqual(e.code, 'ESRCH'); // Already gone. + // Generally ESRCH is returned when the process group is already gone. On + // some platforms such as OS X it may be EPERM though. + assert.ok((e.code === 'EPERM') || (e.code === 'ESRCH')); } }