Tarantool development patches archive
 help / color / mirror / Atom feed
From: "Alexander V. Tikhonov" <avtikhon@tarantool.org>
To: Alexander Turenko <alexander.turenko@tarantool.org>
Cc: "Alexander V. Tikhonov" <avtikhon@tarantool.org>,
	tarantool-patches@freelists.org
Subject: [tarantool-patches] [PATCH v1] test: avoid of too long running sql-tap tests
Date: Mon,  2 Sep 2019 08:53:30 +0300	[thread overview]
Message-ID: <baed061c8374d5d0b5792eeba0dee0f7d32ba0a0.1567402294.git.avtikhon@tarantool.org> (raw)

The test sql-tap/gh-3083-ephemeral-unref-tuples.test.lua took
too long runtime and failed to finish in timeout limit of 2
minutes when it runs near the end of the running queue:

No output during 120 seconds. Will abort after 120 seconds without output. List of workers not reporting the status:
- 012_sql-tap [sql-tap/gh-3083-ephemeral-unref-tuples.test.lua, vinyl] at var/012_sql-tap/gh-3083-ephemeral-unref-tuples.result:0
Test hung! Result content mismatch:
[File does not exists: sql-tap/gh-3083-ephemeral-unref-tuples.result]
[Main process] No output from workers. It seems that we hang. Send SIGKILL to workers; exiting...

Due to suggestion from Konstantin Osipov at gh-3845:
https://github.com/tarantool/tarantool/issues/3845#issue-385735959

The following tests:
  gh-3083-ephemeral-unref-tuples.test.lua
  gh-3332-tuple-format-leak.test.lua
where set to run only on memtx configuration.

Also the test:
  gh-3083-ephemeral-unref-tuples.test.lua
was removed from the test-run 'fragile' option flaky list.

Closed #4128
---

Github: https://github.com/tarantool/tarantool/tree/avtikhon/gh-4128-disable-vinyl-test-3083
Issue: https://github.com/tarantool/tarantool/issues/4128

 test/sql-tap/engine.cfg | 6 ++++++
 test/sql-tap/suite.ini  | 3 +--
 2 files changed, 7 insertions(+), 2 deletions(-)

diff --git a/test/sql-tap/engine.cfg b/test/sql-tap/engine.cfg
index dc64bbdbc..693a477b7 100644
--- a/test/sql-tap/engine.cfg
+++ b/test/sql-tap/engine.cfg
@@ -14,6 +14,12 @@
     "sort.test.lua": {
         "memtx": {"engine": "memtx"}
     },
+    "gh-3083-ephemeral-unref-tuples.test.lua": {
+        "memtx": {"engine": "memtx"}
+    },
+    "gh-3332-tuple-format-leak.test.lua": {
+        "memtx": {"engine": "memtx"}
+    },
     "gh-4077-iproto-execute-no-bind.test.lua": {},
     "*": {
         "memtx": {"engine": "memtx"},
diff --git a/test/sql-tap/suite.ini b/test/sql-tap/suite.ini
index ec10383ae..8f3c3eab1 100644
--- a/test/sql-tap/suite.ini
+++ b/test/sql-tap/suite.ini
@@ -29,6 +29,5 @@ long_run = gh-3332-tuple-format-leak.test.lua, gh-3083-ephemeral-unref-tuples.te
 config = engine.cfg
 show_reproduce_content = False
 pretest_clean = True
-fragile = gh-3083-ephemeral-unref-tuples.test.lua ; gh-4128
-          gh-4077-iproto-execute-no-bind.test.lua ; gh-4459
+fragile = gh-4077-iproto-execute-no-bind.test.lua ; gh-4459
           selectG.test.lua                        ; gh-4458
-- 
2.17.1

             reply	other threads:[~2019-09-02  5:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-02  5:53 Alexander V. Tikhonov [this message]
2019-09-02 11:22 ` [tarantool-patches] " Alexander Turenko

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=baed061c8374d5d0b5792eeba0dee0f7d32ba0a0.1567402294.git.avtikhon@tarantool.org \
    --to=avtikhon@tarantool.org \
    --cc=alexander.turenko@tarantool.org \
    --cc=tarantool-patches@freelists.org \
    --subject='Re: [tarantool-patches] [PATCH v1] test: avoid of too long running sql-tap tests' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox