From 7a4dfb6aa8544805a638bf59d07648b1b6ce8142 Mon Sep 17 00:00:00 2001 From: Bert Belder Date: Wed, 20 Jun 2012 00:56:33 +0200 Subject: [PATCH] test-cluster-worker-kill: use SIGKILL instead of SIGHUP In this test sending SIGKILL has the same effect as sending SIGHUP, but SIGKILL has the advantage that it works on Windows too. --- test/simple/test-cluster-worker-kill.js | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/test/simple/test-cluster-worker-kill.js b/test/simple/test-cluster-worker-kill.js index 9fd13ad65ef..284b83e7fe2 100644 --- a/test/simple/test-cluster-worker-kill.js +++ b/test/simple/test-cluster-worker-kill.js @@ -21,7 +21,7 @@ // test-cluster-worker-kill.js -// verifies that, when a child process is killed (we use SIGHUP) +// verifies that, when a child process is killed (we use SIGKILL) // - the parent receives the proper events in the proper order, no duplicates // - the exitCode and signalCode are correct in the 'exit' event // - the worker.suicide flag, and worker.state are correct @@ -40,7 +40,7 @@ if (cluster.isWorker) { } else if (cluster.isMaster) { - var KILL_SIGNAL = 'SIGHUP', + var KILL_SIGNAL = 'SIGKILL', expected_results = { cluster_emitDisconnect: [1, "the cluster did not emit 'disconnect'"], cluster_emitExit: [1, "the cluster did not emit 'exit'"],