Tarantool development patches archive
 help / color / mirror / Atom feed
From: Alexander Turenko <alexander.turenko@tarantool.org>
To: "Alexander V. Tikhonov" <avtikhon@tarantool.org>
Cc: Oleg Piskunov <o.piskunov@tarantool.org>,
	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 14:29:33 +0300	[thread overview]
Message-ID: <20200521112933.ps2uhwbvkeste6ze@tkn_work_nb> (raw)
In-Reply-To: <7f8b7e281522a7d1f7a723f7756f0c4e3be86c51.1590046682.git.avtikhon@tarantool.org>

LGTM.

(But should NOT be pushed to master until I'll push test-run fix from PR
#211.)

Left a couple of nits, however. See below.

WBR, Alexander Turenko.

> 60f84cbf ('test: use unix sockets for iproto connections')

Nit: We mention commits in the form
0000000000000000000000000000000000000000 ('commit message header'): full
40-digits hash and the commit message header. You'll need to carry the
header when will use full commit hash and it is okay.

Personally I think that short hashes lookes better when used inline
within a text and that our style will recommend them sooner or later.
But now it is not so.

> diff --git a/test/app-tap/tarantoolctl.test.lua b/test/app-tap/tarantoolctl.test.lua
> index 4d7059559..dd90c8a25 100755
> --- a/test/app-tap/tarantoolctl.test.lua
> +++ b/test/app-tap/tarantoolctl.test.lua
> @@ -465,12 +465,9 @@ else
>      local remote_path = create_script(dir, 'remote.lua', remote_code)
>      test_run:cmd(("create server remote with script='%s'"):format(remote_path))
>      test_run:cmd("start server remote")
> -    local port = tonumber(
> -        test_run:eval("remote",
> -                      "return require('uri').parse(box.cfg.listen).service")[1]
> -    )
> +    local admin_socket = test_run:eval("remote", "return box.cfg.listen")[1]

Nit: Admin port / socket usually refer a console port / socket. I would
name the variable `listen_url` or `remote_uri`. The former is used
several times across tests and also is part of `return_listen_uri`
option name.

  reply	other threads:[~2020-05-21 11:29 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 [this message]
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
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=20200521112933.ps2uhwbvkeste6ze@tkn_work_nb \
    --to=alexander.turenko@tarantool.org \
    --cc=avtikhon@tarantool.org \
    --cc=o.piskunov@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