[Tarantool-patches] [PATCH v1] test: flaky sql/gh2483-remote-persistency-* test

[Alexander V. Tikhonov]

Found issue:

  No output during 120 seconds. Will abort after 120 seconds without output. List of workers not reporting the status:
  Test hung! Result content mismatch:

   - [1]
   ...
   test_run:cmd("restart server default")
  --- Connect to ourself

It happened because test-run used to restart 'tarantoolctl restart'
routine with default signal SIGTERM. After tarantoolctl updated with
the ability to provide needed signal to kill the instance, then SIGKILL
was set in the test.

Part of #5510
---

Github: https://github.com/tarantool/tarantool/tree/avtikhon/gh-5510-hang-gh2483
Issue: https://github.com/tarantool/tarantool/issues/5510

 test/sql/gh2483-remote-persistency-check.result   | 2 +-
 test/sql/gh2483-remote-persistency-check.test.lua | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/test/sql/gh2483-remote-persistency-check.result b/test/sql/gh2483-remote-persistency-check.result
index 3ee49b349..185629827 100644
--- a/test/sql/gh2483-remote-persistency-check.result
+++ b/test/sql/gh2483-remote-persistency-check.result
@@ -32,7 +32,7 @@ box.execute([[SELECT * FROM t]])
   rows:
   - [1]
 ...
-test_run:cmd('restart server default');
+test_run:cmd('restart server default with signal=KILL');
 -- Connect to ourself
 c = require('net.box').connect(os.getenv("LISTEN"))
 ---
diff --git a/test/sql/gh2483-remote-persistency-check.test.lua b/test/sql/gh2483-remote-persistency-check.test.lua
index b36b402fb..fca8dad47 100644
--- a/test/sql/gh2483-remote-persistency-check.test.lua
+++ b/test/sql/gh2483-remote-persistency-check.test.lua
@@ -13,7 +13,7 @@ box.execute([[INSERT INTO t (id) VALUES (1)]])
 -- Sanity check
 box.execute([[SELECT * FROM t]])
 
-test_run:cmd('restart server default');
+test_run:cmd('restart server default with signal=KILL');
 
 -- Connect to ourself
 c = require('net.box').connect(os.getenv("LISTEN"))
-- 
2.25.1