Tarantool development patches archive
 help / color / mirror / Atom feed
From: "Alexander V. Tikhonov" <avtikhon@tarantool.org>
To: Alexander Turenko <alexander.turenko@tarantool.org>
Cc: tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH v2] test: set unix sockets for iproto at core = app
Date: Thu, 21 May 2020 22:37:35 +0300	[thread overview]
Message-ID: <20200521193735.GA27679@hpalx> (raw)
In-Reply-To: <20200521175303.rpc5lrpnghfkzsc3@tkn_work_nb>

Alexander, thank you for the correction, removed the test from the
fragiled list and mentioned it in the commit message.

On Thu, May 21, 2020 at 08:53:03PM +0300, Alexander Turenko wrote:
> > Closes #4459
> > ---
> 
> > diff --git a/test/sql-tap/suite.ini b/test/sql-tap/suite.ini
> > index 8f3c3eab1..0e8498875 100644
> > --- a/test/sql-tap/suite.ini
> > +++ b/test/sql-tap/suite.ini
> > @@ -29,5 +29,6 @@ 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
> > +use_unix_sockets_iproto = True
> >  fragile = gh-4077-iproto-execute-no-bind.test.lua ; gh-4459
> >            selectG.test.lua                        ; gh-4458
> 
> We added gh-4077-iproto-execute-no-bind.test.lua test into fragile test
> list because of the 'Address already in use' problem, which we're going
> to workaround here. So it worth to remove the test from the fragile test
> list.

  reply	other threads:[~2020-05-21 19:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-21  7:45 Alexander V. Tikhonov
2020-05-21 11:29 ` Alexander Turenko
2020-05-21 11:38   ` Alexander V. Tikhonov
2020-05-22 12:50     ` Oleg Piskunov
2020-05-21 17:53 ` Alexander Turenko
2020-05-21 19:37   ` Alexander V. Tikhonov [this message]
2020-05-28  7:36 ` Kirill Yukhin

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=20200521193735.GA27679@hpalx \
    --to=avtikhon@tarantool.org \
    --cc=alexander.turenko@tarantool.org \
    --cc=tarantool-patches@dev.tarantool.org \
    --subject='Re: [Tarantool-patches] [PATCH v2] test: set unix sockets for iproto at core = app' \
    /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