Tarantool development patches archive
 help / color / mirror / Atom feed
From: Alexander Turenko <alexander.turenko@tarantool.org>
To: "Alexander V. Tikhonov" <avtikhon@tarantool.org>
Cc: tarantool-patches@freelists.org,
	Georgy Kirichenko <georgy@tarantool.org>
Subject: [tarantool-patches] Re: [PATCH v2 2/2] test: added loop with restart for fullmesh routine
Date: Sun, 24 Mar 2019 08:41:51 +0300	[thread overview]
Message-ID: <20190324054150.57crfwhsfursfw66@tkn_work_nb> (raw)
In-Reply-To: <463a0c7cf85bf52ce80a27ac356a850ac789e442.1553148177.git.avtikhon@tarantool.org>

I created more or less minimal test case for the problem on the branch
Totktonada/reproduce-create-cluster-fail (./run.sh reproduces the
problem). Hope Georgy will able to pay some time to look into (CCed
him).

I think that we should not hide non-investigated problems in such way
except, maybe, really urgent cases, only as temporary workaround and
with a reference to an issue about a real problem (to don't forget to
revert after a fix).

If we'll decide to do that retries we should do it in test_run.lua (I
guess in create_cluster()).

Let's wait for an initial investigation from Georgy or one of other
developers.

WBR, Alexander Turenko.

On Thu, Mar 21, 2019 at 09:03:06AM +0300, Alexander V. Tikhonov wrote:
> Add loop with restart for fullmesh routine.
> ---
>  test/replication/autobootstrap.result              | 3 ++-
>  test/replication/autobootstrap.test.lua            | 2 +-
>  test/replication/autobootstrap_guest.result        | 2 +-
>  test/replication/autobootstrap_guest.test.lua      | 2 +-
>  test/replication/before_replace.result             | 2 +-
>  test/replication/before_replace.test.lua           | 2 +-
>  test/replication/ddl.result                        | 2 +-
>  test/replication/ddl.test.lua                      | 2 +-
>  test/replication/misc.result                       | 2 +-
>  test/replication/misc.test.lua                     | 2 +-
>  test/replication/on_replace.result                 | 2 +-
>  test/replication/on_replace.test.lua               | 2 +-
>  test/replication/quorum.result                     | 4 ++--
>  test/replication/quorum.test.lua                   | 4 ++--
>  test/replication/rebootstrap.result                | 2 +-
>  test/replication/rebootstrap.test.lua              | 2 +-
>  test/replication/recover_missing_xlog.result       | 9 ++-------
>  test/replication/recover_missing_xlog.test.lua     | 7 ++-----
>  test/replication/replicaset_ro_mostly.result       | 1 +
>  test/replication/show_error_on_disconnect.result   | 2 +-
>  test/replication/show_error_on_disconnect.test.lua | 2 +-
>  21 files changed, 26 insertions(+), 32 deletions(-)

  reply	other threads:[~2019-03-24  5:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-21  6:03 [tarantool-patches] [PATCH v2 1/2] test: tunned timeouts and added statuses checks Alexander V. Tikhonov
2019-03-21  6:03 ` [tarantool-patches] [PATCH v2 2/2] test: added loop with restart for fullmesh routine Alexander V. Tikhonov
2019-03-24  5:41   ` Alexander Turenko [this message]
2019-03-24  7:19 ` [tarantool-patches] Re: [PATCH v2 1/2] test: tunned timeouts and added statuses checks 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=20190324054150.57crfwhsfursfw66@tkn_work_nb \
    --to=alexander.turenko@tarantool.org \
    --cc=avtikhon@tarantool.org \
    --cc=georgy@tarantool.org \
    --cc=tarantool-patches@freelists.org \
    --subject='[tarantool-patches] Re: [PATCH v2 2/2] test: added loop with restart for fullmesh routine' \
    /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