Tarantool development patches archive
 help / color / mirror / Atom feed
From: "Alexander Tikhonov" <avtikhon@tarantool.org>
To: "Igor Munkin" <imun@tarantool.org>
Cc: tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH v1 1/2] test: use default replication connection timeout
Date: Mon, 20 Jan 2020 08:06:48 +0300	[thread overview]
Message-ID: <1579496808.842181057@f343.i.mail.ru> (raw)
In-Reply-To: <20200114232322.GL31304@tarantool.org>

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

Igor,

Thanks for the review, I've changed the commit message as you suggested.


>Среда, 15 января 2020, 2:25 +03:00 от Igor Munkin <imun@tarantool.org>:
>
>Sasha,
>
>Thanks, the patch LGTM, though as discussed offline I see no relation to
>ASAN. So I propose to reword the commit message as the following:
>| All local connection timeout settings not related to the testing
>| scenario are removed within this change. Instead of removed values the
>| default one from src/box/lua/load_cfg.lua will be used. The approach
>| with a single default value helps to avoid flaky test results
>| regarding different timeout values and makes the future maintainence
>| easier.
>|
>| The change is required for LSAN and ASAN testing machinery since it
>| introduces a little overhead and cause failures for tests with
>| excessively strict time limits.
>|
>| Needed for #2058
>
>Feel free to adjust it on your own way.
>
>On 21.11.19, Alexander V. Tikhonov wrote:
>> Removed all local connection timeout setups, where it is not the part
>> of the testing scenario. Instead of it the default value will be used.
>> Also it is more comfortable to change the single default value instead
>> of the change this value at each of the test scenarios, it will help
>> to avoid of flaky results in tests beacuse of different timeout vlaues.
>
>Typo: s/vlaues/values/.
>Typo: s/beacuse/because/.
>
>> The most of tests used the replication connection timeout is equal to
>> 0.5 second, while defualt value is set at sources file:
>
>Typo: s/defualt/default/.
>
>>     src/box/lua/load_cfg.lua
>> to the value of 30 seconds:
>>     replication_connect_timeout = 30
>> which is quite enough for all of the tests that don't need any special
>> values for it.
>> 
>> Part of #2058
>> ---
>
><snipped>
>
>> -- 
>> 2.17.1
>> 
>
>-- 
>Best regards,
>IM


-- 
Alexander Tikhonov

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

  reply	other threads:[~2020-01-20  5:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-21  8:25 [Tarantool-patches] [PATCH v1 0/2] Add LSAN to ASAN testing Alexander V. Tikhonov
2019-11-21  8:25 ` [Tarantool-patches] [PATCH v1 1/2] test: use default replication connection timeout Alexander V. Tikhonov
2020-01-14 23:23   ` Igor Munkin
2020-01-20  5:06     ` Alexander Tikhonov [this message]
2019-11-21  8:25 ` [Tarantool-patches] [PATCH v1 2/2] gitlab-ci: ASAN testing memory leaks add Alexander V. Tikhonov
2020-01-14 23:23   ` Igor Munkin
2020-01-20  5:26     ` Alexander Tikhonov
2020-04-02  7:53 ` [Tarantool-patches] [PATCH v1 0/2] Add LSAN to ASAN testing 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=1579496808.842181057@f343.i.mail.ru \
    --to=avtikhon@tarantool.org \
    --cc=imun@tarantool.org \
    --cc=tarantool-patches@dev.tarantool.org \
    --subject='Re: [Tarantool-patches] [PATCH v1 1/2] test: use default replication connection timeout' \
    /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