From: Sergey Kaplun via Tarantool-patches <tarantool-patches@dev.tarantool.org> To: Igor Munkin <imun@tarantool.org> Cc: tarantool-patches@dev.tarantool.org Subject: Re: [Tarantool-patches] [PATCH luajit 1/2] test: relax JIT setup in lj-430-maxirconst test Date: Mon, 5 Dec 2022 10:52:53 +0300 [thread overview] Message-ID: <Y42jVcVVpvhit+w0@root> (raw) In-Reply-To: <de5e69b3c7368fe194b5444fbaa03563bfeb53eb.1669926435.git.imun@tarantool.org> Hi, Igor! Thanks for the patch! LGTM, just several nits regarding the commit message. On 01.12.22, Igor Munkin wrote: > JIT engine setup in tarantool-tests/lj-430-maxirconst.test.lua is too > tight for the build with LUAJIT_ENABLE_CHECKHOOK option enabled. > Originally test limits <maxirconst> value with 3 for the default IRRef > constants set: nil, true, false. However, with LUAJIT_ENABLE_CHECKHOOK > enabled there are three more auxiliary IRRef constants for the internal Typo: s/enabled/enabled,/ > purposes. Hence, the test is reimplemented the following way: > * The first trace for the empty function is recorded > * The number of IRRef constants is obtained via <jit.util.traceinfo> > * <maxirconst> parameter is set to this value > * The second trace for the function with a single local variable, > initialized with a constant, fails to record > > As a result there is no need to explicitly respect any configuration. Typo: s/As a result/As a result,/ > > Relates to tarantool/tarantool#7762 > > Signed-off-by: Igor Munkin <imun@tarantool.org> > --- > .../lj-430-maxirconst.test.lua | 23 +++++++++++-------- > 1 file changed, 14 insertions(+), 9 deletions(-) <snipped> > 2.34.0 > -- Best regards, Sergey Kaplun
next prev parent reply other threads:[~2022-12-05 7:56 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-01 20:28 [Tarantool-patches] [PATCH luajit 0/2] Fix tests for LUAJIT_ENABLE_CHECKHOOK Igor Munkin via Tarantool-patches 2022-12-01 20:28 ` [Tarantool-patches] [PATCH luajit 1/2] test: relax JIT setup in lj-430-maxirconst test Igor Munkin via Tarantool-patches 2022-12-05 7:52 ` Sergey Kaplun via Tarantool-patches [this message] 2022-12-05 21:33 ` Igor Munkin via Tarantool-patches 2022-12-05 10:47 ` Maxim Kokryashkin via Tarantool-patches 2022-12-05 21:34 ` Igor Munkin via Tarantool-patches 2022-12-01 20:28 ` [Tarantool-patches] [PATCH luajit 2/2] test: relax JIT setup in misc.getmetrics test Igor Munkin via Tarantool-patches 2022-12-05 7:57 ` Sergey Kaplun via Tarantool-patches 2022-12-05 21:40 ` Igor Munkin via Tarantool-patches 2022-12-05 10:52 ` Maxim Kokryashkin via Tarantool-patches 2022-12-05 21:40 ` Igor Munkin via Tarantool-patches 2022-12-02 10:01 ` [Tarantool-patches] [PATCH luajit 3/2] test: remove TAP side effects in getmetrics tests Igor Munkin via Tarantool-patches 2022-12-05 8:01 ` Sergey Kaplun via Tarantool-patches 2022-12-05 21:46 ` Igor Munkin via Tarantool-patches 2022-12-05 11:06 ` Maxim Kokryashkin via Tarantool-patches 2022-12-05 21:47 ` Igor Munkin via Tarantool-patches 2022-12-02 10:05 ` [Tarantool-patches] [PATCH luajit 0/2] Fix tests for LUAJIT_ENABLE_CHECKHOOK Igor Munkin via Tarantool-patches 2022-12-12 9:42 ` 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=Y42jVcVVpvhit+w0@root \ --to=tarantool-patches@dev.tarantool.org \ --cc=imun@tarantool.org \ --cc=skaplun@tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH luajit 1/2] test: relax JIT setup in lj-430-maxirconst test' \ /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