Tarantool development patches archive
 help / color / mirror / Atom feed
From: "Sergei Voronezhskii" <sergw@tarantool.org>
To: "Alexander Turenko" <alexander.turenko@tarantool.org>
Cc: tarantool-patches@freelists.org,
	"Vladimir Davydov" <vdavydov.dev@gmail.com>
Subject: Re[2]: [PATCH 1/2] test: wait until expected value appear in log
Date: Tue, 23 Oct 2018 18:00:52 +0300	[thread overview]
Message-ID: <1540306852.113865434@f466.i.mail.ru> (raw)
In-Reply-To: <20181021044032.nqymxhhczdco5hxh@tkn_work_nb>

[-- Attachment #1: Type: text/plain, Size: 1618 bytes --]


>Воскресенье, 21 октября 2018, 7:40 +03:00 от Alexander Turenko <alexander.turenko@tarantool.org>:
>
>>  fio.basename(snaps[1], '.snap') >= fio.basename(xlogs[1], '.xlog')
>> 
>>  -- gh-2780 check that scheduled snapshots are performed
>> -fiber.sleep(3 * PERIOD)
>> --- check that it's not first snapshot
>> -test_run:grep_log("default", "saving snapshot", 400) == nil
>> -test_run:grep_log("default", "making snapshot", 400) ~= nil
>> +test_run:wait_log("default", "making snapshot", 400, 1.0 + PERIOD)
>> 
>>  -- restore default options
>>  box.cfg{checkpoint_interval = 3600 * 4, checkpoint_count = 4 }
>
>Cite from the previous review:
>
>> >  -- gh-2780 check that scheduled snapshots are performed
>> > -fiber.sleep(3 * PERIOD)
>> >  -- check that it's not first snapshot
>> > -test_run:grep_log("default", "saving snapshot", 400) == nil
>> > -test_run:grep_log("default", "making snapshot", 400) ~= nil
>> > +wait_cond(function() return test_run:grep_log("default", "saving snapshot", 400) == nil end)
>> > +wait_cond(function() return test_run:grep_log("default", "making snapshot", 400) ~= nil end)
>
>> Now we don't check that 'saving snapshot' does not appear during some
>> time period. Maybe we should check it after 'making snapshot'.
>
>It seems you decided to remove the check for some reason you don't mention in
>the commit message. Am I missed something obvious?
>
>In the previous message I just stated that **your** (previous) version of the
>patch does not check for 'saving snapshot' while the original case does.
>
>WBR, Alexander Turenko.
Fixed


-- 
Sergei Voronezhskii

[-- Attachment #2: Type: text/html, Size: 2310 bytes --]

  reply	other threads:[~2018-10-23 15:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-10  7:56 [PATCH] test: enable parallel mode for xlog tests Sergei Voronezhskii
2018-10-10  7:56 ` [PATCH 1/2] test: wait until expected value appear in log Sergei Voronezhskii
2018-10-15  0:29   ` Alexander Turenko
2018-10-17 22:04     ` [PATCH] test: enable parallel mode for xlog tests Sergei Voronezhskii
2018-10-17 22:04       ` [PATCH 1/2] test: wait until expected value appear in log Sergei Voronezhskii
2018-10-21  4:40         ` Alexander Turenko
2018-10-23 15:00           ` Sergei Voronezhskii [this message]
2018-10-25  2:49             ` Alexander Turenko
2018-10-17 22:04       ` [PATCH 2/2] test: enable parallel mode for xlog tests Sergei Voronezhskii
2018-11-27 13:33         ` [tarantool-patches] " Sergei Voronezhskii
2018-11-28 14:42       ` [tarantool-patches] [PATCH] " Kirill Yukhin
2018-10-10  7:56 ` [PATCH 2/2] " 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=1540306852.113865434@f466.i.mail.ru \
    --to=sergw@tarantool.org \
    --cc=alexander.turenko@tarantool.org \
    --cc=tarantool-patches@freelists.org \
    --cc=vdavydov.dev@gmail.com \
    --subject='Re: Re[2]: [PATCH 1/2] test: wait until expected value appear in log' \
    /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