From: Igor Munkin via Tarantool-patches <tarantool-patches@dev.tarantool.org>
To: Sergey Ostanevich <sergos@tarantool.org>
Cc: tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH luajit 1/3] test: add PUC-Rio Lua 5.1 test suite
Date: Wed, 17 Mar 2021 18:17:23 +0300 [thread overview]
Message-ID: <20210317151723.GC29703@tarantool.org> (raw)
In-Reply-To: <91E86450-7252-44D8-B6DA-001FD393FB1A@tarantool.org>
Sergos,
Thanks for you review!
On 16.03.21, Sergey Ostanevich wrote:
> Hi!
>
> Thanks for the patch!
>
>
>
> > On 12 Mar 2021, at 08:36, Sergey Kaplun <skaplun@tarantool.org> wrote:
> >
> > This patch adds PUC-Rio Lua 5.1 test suite as a part of the LuaJIT
> > test suite. Source code taken verbatim from
> > https://www.lua.org/tests/lua5.1-tests.tar.gz.
> >
> > <lib1.c> and <lib2.c> is slightly modified to be consistent with the
> > current LuaJIT's LuaC API.
> >
>
> This should be a different commit, isn’t it?
Yes, it does.
>
> > Some tests may fail after this commit. They will be disabled
> > or adapted in the next patches.
>
> The fact patch causes - even temporarily - some fails is no good. The
> only exception is initial commit, that brings original test suite.
> Can you please make a consistent change that will left the tests disabled
> until they adapted and enabled back?
I believe such juggling with enabling/disabling is quite unprofitable.
We iteratively fix broken tests within the series making CI green as a
result. Even if lib[12].c fails to compile -- it is not a problem, since
these libraries are test dependencies, not build ones. Sergey can simply
mention the fact the build of suite-related tests is broken, so one can
find the comment in commit message while e.g. bisecting the bug.
Otherwise, the patches are spoiled with unnecessary changes.
>
> regards,
> Sergos
>
> >
<snipped>
> > --
> > 2.28.0
> >
>
--
Best regards,
IM
next prev parent reply other threads:[~2021-03-17 15:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-12 5:36 [Tarantool-patches] [PATCH luajit 0/3] Adapt " Sergey Kaplun via Tarantool-patches
2021-03-12 5:36 ` [Tarantool-patches] [PATCH luajit 1/3] test: add " Sergey Kaplun via Tarantool-patches
2021-03-16 13:35 ` Sergey Ostanevich via Tarantool-patches
2021-03-17 15:17 ` Igor Munkin via Tarantool-patches [this message]
2021-03-19 11:30 ` Sergey Kaplun via Tarantool-patches
2021-03-17 14:55 ` Igor Munkin via Tarantool-patches
2021-03-19 11:26 ` Sergey Kaplun via Tarantool-patches
2021-03-12 5:36 ` [Tarantool-patches] [PATCH luajit 2/3] test: adapt PUC-Rio Lua 5.1 test suite for LuaJIT Sergey Kaplun via Tarantool-patches
2021-03-13 19:04 ` Sergey Ostanevich via Tarantool-patches
2021-03-22 18:52 ` Igor Munkin via Tarantool-patches
2021-03-26 8:26 ` Sergey Kaplun via Tarantool-patches
2021-03-12 5:36 ` [Tarantool-patches] [PATCH luajit 3/3] test: adapt Lua 5.1 test suite for Tarantool Sergey Kaplun via Tarantool-patches
2021-03-13 19:07 ` Sergey Ostanevich 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=20210317151723.GC29703@tarantool.org \
--to=tarantool-patches@dev.tarantool.org \
--cc=imun@tarantool.org \
--cc=sergos@tarantool.org \
--subject='Re: [Tarantool-patches] [PATCH luajit 1/3] test: add PUC-Rio Lua 5.1 test suite' \
/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