]
Galder Zamarreño resolved HRJS-25.
----------------------------------
Fix Version/s: (was: 0.4.0)
Resolution: Rejected
Solved independently by HRJS-30 where no pkill command is needed any more.
Test pkill command might be killing itself
------------------------------------------
Key: HRJS-25
URL:
https://issues.jboss.org/browse/HRJS-25
Project: Infinispan Javascript client
Issue Type: Bug
Affects Versions: 0.3.0
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
In some environments (e.g. ubuntu), failover and xsite tests fail 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:854:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:222:5)
{code}
After adding more info the error, we've found that the error contains:
{code}
exec error (JS):
{"killed":false,"code":null,"signal":"SIGKILL","cmd":"/bin/sh
-c pkill -9 -f '.*java.*node4 .*'"}
{code}
The node.js documentation says:
{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 might imply that the {{pkill}} command is killing itself...