Tarantool development patches archive
 help / color / mirror / Atom feed
From: Kirill Yukhin <kyukhin@tarantool.org>
To: Nikita Pettik <korablev@tarantool.org>
Cc: tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH] test: stabilize flaky fiber memory leak detection
Date: Fri, 28 Feb 2020 02:07:28 +0300	[thread overview]
Message-ID: <20200227230728.oojzge5o4kkr3ofb@tarantool.org> (raw)
In-Reply-To: <20200227225801.GD12687@tarantool.org>

On 28 фев 01:58, Nikita Pettik wrote:
> On 27 Feb 23:22, Kirill Yukhin wrote:
> > Hello,
> > 
> > > 
> > > Fixes #4750.
> > 
> > I've checked your patch into 2.2, 2.3 and master as temporary
> > workaround.
> 
> Patch got no lgtms btw. Just for the record.

This is temporary, to stabilize testing.

--
Regards, Kirill Yukhin

      reply	other threads:[~2020-02-27 23:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-29 17:03 Alexander Turenko
2020-01-29 18:46 ` Nikita Pettik
2020-01-29 20:27   ` Alexander Turenko
2020-02-05 15:36     ` Nikita Pettik
2020-02-27 20:22 ` Kirill Yukhin
2020-02-27 22:58   ` Nikita Pettik
2020-02-27 23:07     ` Kirill Yukhin [this message]

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=20200227230728.oojzge5o4kkr3ofb@tarantool.org \
    --to=kyukhin@tarantool.org \
    --cc=korablev@tarantool.org \
    --cc=tarantool-patches@dev.tarantool.org \
    --subject='Re: [Tarantool-patches] [PATCH] test: stabilize flaky fiber memory leak detection' \
    /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