Tarantool development patches archive
 help / color / mirror / Atom feed
From: Alexander Turenko <alexander.turenko@tarantool.org>
To: Sergei Voronezhskii <sergw@tarantool.org>
Cc: tarantool-patches@freelists.org,
	Vladimir Davydov <vdavydov.dev@gmail.com>
Subject: Re: [PATCH v2 0/5] test: replication parallel mode on
Date: Wed, 31 Oct 2018 21:28:28 +0300	[thread overview]
Message-ID: <20181031182828.2aqwvcari7d2pqiv@tkn_work_nb> (raw)
In-Reply-To: <1540921104.5696206@f485.i.mail.ru>

> >>I also observed a fail and a hang on box/:
> >>
> >>https://travis-ci.org/tarantool/tarantool/jobs/443475294#L2496
> >>https://travis-ci.org/tarantool/tarantool/jobs/443475296#L6173
> >>
> >>Maybe test-run do something incorrect and the suites are not fully
> >>independent in the parallel run? Maybe some tests from box/ and
> >>replication/ conflicts on some global resource, say the same unix socket
> >>name in /tmp?
> >>
> >>Please, try to reproduce the issue and fix / report it.
> >
> >Fixed problem with box/errinj (after adding new errinj, ordering of output 'box.error.injection.info()' changed) 
>
> Problem with engine/ddl is not depends on enabling replication tests in parallel mode.

Please, file an issue re flaky test even if you do not have much details
at the time.

So it seems I have no more comments. Please, proceed with Vova.

> >
> >>
> >>WBR, Alexander Turenko.
> >>
> >>On Sat, Oct 20, 2018 at 02:37:01AM +0300, Alexander Turenko wrote:
> >>> It seems you catched segfault on the replication suite with this patch
> >>> :)
> >>> 
> >>>  https://travis-ci.org/tarantool/tarantool/jobs/443475291#L2591

To track: it was introduced in the patch and was fixed. See [1] for
details.

[1]: https://github.com/tarantool/tarantool/issues/3765

WBR, Alexander Turenko.

  reply	other threads:[~2018-10-31 18:28 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-19 16:17 Sergei Voronezhskii
2018-10-19 16:17 ` [PATCH v2 1/5] test: cleanup replication tests Sergei Voronezhskii
2018-10-21 20:41   ` Alexander Turenko
2018-10-22  8:07     ` Re[2]: " Sergei Voronezhskii
2018-10-23  3:21       ` Alexander Turenko
2018-10-19 16:17 ` [PATCH v2 2/5] test: errinj for pause relay_send Sergei Voronezhskii
2018-10-21 20:41   ` Alexander Turenko
2018-10-22  8:42     ` Re[2]: " Sergei Voronezhskii
2018-10-23  3:22       ` Alexander Turenko
2018-10-19 16:17 ` [PATCH v2 3/5] test: put require in proper places Sergei Voronezhskii
2018-10-21 20:41   ` Alexander Turenko
2018-10-19 16:17 ` [PATCH v2 4/5] test: use wait_cond to check follow status Sergei Voronezhskii
2018-10-19 23:24   ` Alexander Turenko
2018-10-25 16:43     ` [tarantool-patches] " Sergei Voronezhskii
2018-10-29 10:41       ` Alexander Turenko
2018-10-31 21:38         ` Re[2]: " Sergei Voronezhskii
2018-10-19 16:17 ` [PATCH v2 5/5] test: replication parallel mode on Sergei Voronezhskii
2018-10-19 23:37 ` [PATCH v2 0/5] " Alexander Turenko
2018-10-19 23:44   ` Alexander Turenko
2018-10-26 12:41     ` Re[2]: " Sergei Voronezhskii
2018-10-26 12:44     ` Sergei Voronezhskii
2018-10-30 17:38       ` Re[3]: " Sergei Voronezhskii
2018-10-31 18:28         ` Alexander Turenko [this message]
2018-11-26 13:04           ` Re[2]: " Sergei Voronezhskii
2018-12-05  4:44             ` Re[3]: " Sergei Voronezhskii

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=20181031182828.2aqwvcari7d2pqiv@tkn_work_nb \
    --to=alexander.turenko@tarantool.org \
    --cc=sergw@tarantool.org \
    --cc=tarantool-patches@freelists.org \
    --cc=vdavydov.dev@gmail.com \
    --subject='Re: [PATCH v2 0/5] test: replication parallel mode on' \
    /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