Galder Zamarreño created HRJS-28:
------------------------------------
Summary: Node kill pkill commands failing in some envs
Key: HRJS-28
URL:
https://issues.jboss.org/browse/HRJS-28
Project: Infinispan Javascript client
Issue Type: Enhancement
Affects Versions: 0.3.0
Reporter: Galder Zamarreño
On certain environments (e.g. Ubuntu), tests involving killing nodes are failing with
errors like this:
{code}
1) Infinispan cluster client can failover when nodes crash
Message:
Error: Command failed: /bin/sh -c pkill -9 -f '.*java.*node4 .*'
Stacktrace:
Error: Command failed: /bin/sh -c pkill -9 -f '.*java.*node4 .*'
at ChildProcess.exithandler (child_process.js:213:12)
at emitTwo (events.js:87:13)
at ChildProcess.emit (events.js:172:7)
at maybeClose (internal/child_process.js:821:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5)
...
5) Infinispan xsite cluster client can manually switch and fail over sites
Message:
Error: Command failed: /bin/sh -c pkill -9 -f '.*java.*node-site-a .*'
Stacktrace:
Error: Command failed: /bin/sh -c pkill -9 -f '.*java.*node-site-a .*'
at ChildProcess.exithandler (child_process.js:213:12)
at emitTwo (events.js:87:13)
at ChildProcess.emit (events.js:172:7)
at maybeClose (internal/child_process.js:821:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5)
{code}
After doing some debugging, we discovered that the error itself contains this info:
{code}
{"killed":false,"code":null,"signal":"SIGKILL","cmd":"/bin/sh
-c pkill -9 -f '.*java.*node4 .*'"}
{code}
According to the docu:
{code}
If the process terminated normally, code is the final exit code of the process, otherwise
null. If the process terminated due to receipt of a signal, signal is the string name of
the signal, otherwise null.
{code}
So, it would appear that {{pkill}} is killing itself?
The easiest workaround here might be to ignore any errors.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)