Tarantool development patches archive
 help / color / mirror / Atom feed
From: Sergey Bronnikov via Tarantool-patches <tarantool-patches@dev.tarantool.org>
To: Sergey Kaplun <skaplun@tarantool.org>
Cc: Sergey Bronnikov <estetus@gmail.com>,
	tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH] test: disable cases in PUC-Rio tests for debug line hook
Date: Mon, 6 Feb 2023 17:01:38 +0300	[thread overview]
Message-ID: <83645195-e845-1aa3-8ea1-d00a1a91d732@tarantool.org> (raw)
In-Reply-To: <Y+D/ibXO3bAI7wfG@root>

Hi, Sergey!


thanks for review! Patch has been updated and force-pushed.


On 2/6/23 16:24, Sergey Kaplun wrote:

<snipped>

>>>> module.
>>>             ^ Those tests rely on specific backtrace, which is changed by
>>>     an additional wrapper for `pairs()`.
>> Added to commit message.
> Nit: "tests" should be in plural form in those sentences as far as the
> only one test (the one with `pairs()` usage) is broken after introducing
> `pairs()` wrapper.

Updated in short and long commit message descriptions.


>
>>
>>>>           Patch disables testcases when running under Tarantool.
>>>>
>>>> 1. https://github.com/tarantool/tarantool/issues/2867
>>>> ---
>>>>    test/PUC-Rio-Lua-5.1-tests/db.lua | 4 ++++
>>>>    1 file changed, 4 insertions(+)
>>>>
>>>> diff --git a/test/PUC-Rio-Lua-5.1-tests/db.lua b/test/PUC-Rio-Lua-5.1-tests/db.lua
>>>> index b148c2dd..b05075bb 100644
>>>> --- a/test/PUC-Rio-Lua-5.1-tests/db.lua
>>>> +++ b/test/PUC-Rio-Lua-5.1-tests/db.lua
>>>> @@ -169,10 +169,12 @@ test([[for i=1,3 do
>>>>    end
>>>>    ]], {1,2,1,2,1,2,1,3})
>>>>    
>>>> +if not _TARANTOOL then
>>> Minor: It will be nice to add the comment about the wrapper for
>>> `pairs()` in Tarantool here.
>>
>> Added:
>>
>> "Tarantool has a wrapper around builtin function `pairs()`, see see gh-2867.
>> Testcase below relies on a specific backtrace, which is changed by an
>> introduced wrapper for `pairs()`."
> Nit: Please, use `--` comment stile, like elsewhere in this file.
> Multiline comments are used for debug tests and for quoting some chunks
> output.
>
> Friendly reminder: Don't forget to change linedefined below:).


Sure, updated:


@@ -169,11 +169,9 @@ test([[for i=1,3 do
  end
  ]], {1,2,1,2,1,2,1,3})

---[[
-Tarantool has a wrapper around builtin function `pairs()`, see see gh-2867.
-Testcase below relies on a specific backtrace, which is changed by an
-introduced wrapper for `pairs()`.
-]]
+-- Tarantool has a wrapper around builtin function `pairs()`, see see 
gh-2867.
+-- Testcase below relies on a specific backtrace, which is changed by an
+-- introduced wrapper for `pairs()`.
  if not _TARANTOOL then
  test([[for i,v in pairs{'a','b'} do
    a=i..v


<snipped>

  reply	other threads:[~2023-02-06 14:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-06  7:44 Sergey Bronnikov via Tarantool-patches
2023-02-06  8:31 ` Sergey Kaplun via Tarantool-patches
2023-02-06 12:17   ` Sergey Bronnikov via Tarantool-patches
2023-02-06 13:24     ` Sergey Kaplun via Tarantool-patches
2023-02-06 14:01       ` Sergey Bronnikov via Tarantool-patches [this message]
2023-02-08 17:23 ` Alexander Turenko via Tarantool-patches
2023-02-09  7:39   ` Sergey Kaplun via Tarantool-patches
2023-02-10 16:18 ` Igor Munkin via Tarantool-patches

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=83645195-e845-1aa3-8ea1-d00a1a91d732@tarantool.org \
    --to=tarantool-patches@dev.tarantool.org \
    --cc=estetus@gmail.com \
    --cc=sergeyb@tarantool.org \
    --cc=skaplun@tarantool.org \
    --subject='Re: [Tarantool-patches] [PATCH] test: disable cases in PUC-Rio tests for debug line hook' \
    /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