From: Sergey Bronnikov via Tarantool-patches <tarantool-patches@dev.tarantool.org> To: Sergey Kaplun <skaplun@tarantool.org> Cc: tarantool-patches@dev.tarantool.org Subject: Re: [Tarantool-patches] [PATCH luajit] test: fix fix-mips64-spare-side-exit-patching Date: Thu, 27 Feb 2025 16:12:30 +0300 [thread overview] Message-ID: <39e85beb-f956-4359-9a40-016d855b0aa1@tarantool.org> (raw) In-Reply-To: <20250227091825.31081-1-skaplun@tarantool.org> [-- Attachment #1: Type: text/plain, Size: 2341 bytes --] Hi, Sergey, thanks for the patch! On 27.02.2025 12:18, Sergey Kaplun wrote: > The aforementioned test is flaky when run under Tarantool due to not > enough room for all traces. The flushing of all traces at the start and > collecting them solves the issue. Have you considered another options like increasing `maxtrace` value? > The same issue may occur for the > <gh-6098-fix-side-exit-patching-on-arm64.test.lua>, so it is adjusted as > well. > --- > > Branch:https://github.com/tarantool/luajit/tree/skaplun/gh-noticket-fix-mips64-flaky-test > To reproduce, run the following command without the patch from the root > of the Tarantool repository: > | ctest --repeat-until-fail 1000 --test-dir third_party/luajit/ -R fix-mips64-spare-side-exit-patching > > .../fix-mips64-spare-side-exit-patching.test.lua | 5 +++++ > .../gh-6098-fix-side-exit-patching-on-arm64.test.lua | 5 +++++ > 2 files changed, 10 insertions(+) > > diff --git a/test/tarantool-tests/fix-mips64-spare-side-exit-patching.test.lua b/test/tarantool-tests/fix-mips64-spare-side-exit-patching.test.lua > index 703d8e69..dd9f2073 100644 > --- a/test/tarantool-tests/fix-mips64-spare-side-exit-patching.test.lua > +++ b/test/tarantool-tests/fix-mips64-spare-side-exit-patching.test.lua > @@ -15,6 +15,11 @@ local MAXTRACE = 2000; > > test:plan(1) > > +-- Flush all possible traces and collect them to be sure that > +-- we have enough space. > +jit.flush() > +collectgarbage() > + > local function find_last_trace() > local candidate = misc.getmetrics().jit_trace_num > for traceno = candidate, MAXTRACE do > diff --git a/test/tarantool-tests/gh-6098-fix-side-exit-patching-on-arm64.test.lua b/test/tarantool-tests/gh-6098-fix-side-exit-patching-on-arm64.test.lua > index 678ac914..f5fc4681 100644 > --- a/test/tarantool-tests/gh-6098-fix-side-exit-patching-on-arm64.test.lua > +++ b/test/tarantool-tests/gh-6098-fix-side-exit-patching-on-arm64.test.lua > @@ -9,6 +9,11 @@ local frontend = require('utils').frontend > > test:plan(1) > > +-- Flush all possible traces and collect them to be sure that > +-- we have enough space. > +jit.flush() > +collectgarbage() > + > -- The function to be tested for side exit patching: > -- * At the beginning of the test case, the <if> branch is > -- recorded as a root trace. [-- Attachment #2: Type: text/html, Size: 3123 bytes --]
next prev parent reply other threads:[~2025-02-27 13:12 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-02-27 9:18 Sergey Kaplun via Tarantool-patches 2025-02-27 13:12 ` Sergey Bronnikov via Tarantool-patches [this message] 2025-02-27 16:05 ` Sergey Kaplun via Tarantool-patches 2025-02-28 13:12 ` Sergey Bronnikov via Tarantool-patches 2025-03-05 7:30 ` Sergey Kaplun 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=39e85beb-f956-4359-9a40-016d855b0aa1@tarantool.org \ --to=tarantool-patches@dev.tarantool.org \ --cc=sergeyb@tarantool.org \ --cc=skaplun@tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH luajit] test: fix fix-mips64-spare-side-exit-patching' \ /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