From: Sergey Ostanevich via Tarantool-patches <tarantool-patches@dev.tarantool.org> To: Sergey Kaplun <skaplun@tarantool.org> Cc: tarantool-patches@dev.tarantool.org Subject: Re: [Tarantool-patches] [WIP luajit 00/15] Adapt LuaVela test suites Date: Fri, 5 Mar 2021 13:48:02 +0300 [thread overview] Message-ID: <7D85A22A-0996-44F3-8748-06E409F27E6D@tarantool.org> (raw) In-Reply-To: <20210304195821.GA745@root> [-- Attachment #1: Type: text/plain, Size: 1249 bytes --] Hi! > On 4 Mar 2021, at 22:58, Sergey Kaplun <skaplun@tarantool.org> wrote: > > On 04.03.21, Sergey Ostanevich wrote: >> Hi! >> >> Thanks for the patchset - brief review >> >> part 1 - obvious, LGTM. >> >> part 2 - LGTM, good to have all follow-ups set. > > Do you mean to reference all follow-ups inside commit message? > There could be just one - if no specific GH created. >> >> part 3 - should have a follow-up ticket to cover all suppressions, if we plan to fix them. > > Ditto. > There are some follow ups that can be grepped by qa and luajit labels. > And this is something I don’t want to do - to grep using lables. The patch should have reference, so I can see all links at once. >> >> part 4-8 are LGTM >> >> part 9 (_G and some modules in Tarantool are different): Are we plan to fix it in some way? There should be a follow-up then. > > For now I can't see any good solution, except ignoring them by special > option like slow tests. > I don’t object to ignore them. My question if we plan to tweak the tests to align with Tarantool? What will happen to the test if Tarantool will change preloaded modules? >> >> parts 10-15 are LGTM >> >> Regards, >> Sergos [-- Attachment #2: Type: text/html, Size: 10221 bytes --]
next prev parent reply other threads:[~2021-03-05 10:48 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-04 10:23 Sergey Kaplun via Tarantool-patches 2021-03-04 10:23 ` [Tarantool-patches] [WIP luajit 01/15] test: add PUC-Rio Lua 5.1 test suite Sergey Kaplun via Tarantool-patches 2021-03-04 10:23 ` [Tarantool-patches] [WIP luajit 02/15] test: adapt PUC-Rio Lua 5.1 test suite for LuaJIT Sergey Kaplun via Tarantool-patches 2021-03-04 10:23 ` [Tarantool-patches] [WIP luajit 03/15] test: adapt Lua 5.1 test suite for Tarantool Sergey Kaplun via Tarantool-patches 2021-03-04 10:23 ` [Tarantool-patches] [WIP luajit 04/15] test: add LuaJIT-test-cleanup test suite Sergey Kaplun via Tarantool-patches 2021-03-04 10:23 ` [Tarantool-patches] [WIP luajit 05/15] test: change tests to match de5568e Sergey Kaplun via Tarantool-patches 2021-03-04 10:23 ` [Tarantool-patches] [WIP luajit 06/15] test: change tests to match c198167 Sergey Kaplun via Tarantool-patches 2021-03-04 10:23 ` [Tarantool-patches] [WIP luajit 07/15] test: change tests to match 5a61e1a Sergey Kaplun via Tarantool-patches 2021-03-04 10:23 ` [Tarantool-patches] [WIP luajit 08/15] test: change LuaJIT suite tests to match b4e6bf0 Sergey Kaplun via Tarantool-patches 2021-03-04 10:23 ` [Tarantool-patches] [WIP luajit 09/15] test: adjust LuaJIT test suite for Tarantool Sergey Kaplun via Tarantool-patches 2021-03-04 10:23 ` [Tarantool-patches] [WIP luajit 10/15] test: add lua-Harness test suite Sergey Kaplun via Tarantool-patches 2021-03-04 10:23 ` [Tarantool-patches] [WIP luajit 11/15] test: adjust lua-Harness test suite for Tarantool Sergey Kaplun via Tarantool-patches 2021-03-04 10:23 ` [Tarantool-patches] [WIP luajit 12/15] test: disable 305-utf8 of lua-Harness suite Sergey Kaplun via Tarantool-patches 2021-03-04 10:24 ` [Tarantool-patches] [WIP luajit 13/15] test: disable 241-standalone " Sergey Kaplun via Tarantool-patches 2021-03-04 10:24 ` [Tarantool-patches] [WIP luajit 14/15] test: disable 411-luajit " Sergey Kaplun via Tarantool-patches 2021-03-04 10:24 ` [Tarantool-patches] [WIP luajit 15/15] test: skip test for getenv in 309-os.t Sergey Kaplun via Tarantool-patches 2021-03-04 16:24 ` [Tarantool-patches] [WIP luajit 00/15] Adapt LuaVela test suites Sergey Ostanevich via Tarantool-patches 2021-03-04 19:58 ` Sergey Kaplun via Tarantool-patches 2021-03-05 10:48 ` Sergey Ostanevich via Tarantool-patches [this message] 2021-03-16 11:21 ` Igor Munkin via Tarantool-patches 2021-03-09 23:59 ` Igor Munkin via Tarantool-patches 2021-03-10 8:09 ` Sergey Kaplun via Tarantool-patches 2021-03-10 10:39 ` Igor Munkin via Tarantool-patches 2021-03-10 9:46 ` Sergey Ostanevich via Tarantool-patches 2021-03-10 10:43 ` Igor Munkin via Tarantool-patches 2021-03-10 16:25 ` 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=7D85A22A-0996-44F3-8748-06E409F27E6D@tarantool.org \ --to=tarantool-patches@dev.tarantool.org \ --cc=sergos@tarantool.org \ --cc=skaplun@tarantool.org \ --subject='Re: [Tarantool-patches] [WIP luajit 00/15] Adapt LuaVela test suites' \ /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