From: Sergey Kaplun via Tarantool-patches <tarantool-patches@dev.tarantool.org> To: Sergey Bronnikov <sergeyb@tarantool.org> Cc: tarantool-patches@dev.tarantool.org Subject: Re: [Tarantool-patches] [PATCH luajit v1 3/5] test: allow `jit.parse` to return aborted traces Date: Thu, 13 Jun 2024 13:00:43 +0300 [thread overview] Message-ID: <ZmrDSzpiWgOgcZIb@root> (raw) In-Reply-To: <42b64daf-a9f6-4267-9d22-4c8d7b88fdca@tarantool.org> Hi, Sergey! Thanks for the review! On 06.06.24, Sergey Bronnikov wrote: > Sergey, > > > thanks for the patch! Please see my comments below. > > On 22.04.2024 11:49, Sergey Kaplun wrote: > > Now information about the abort of the trace is saved in the > > `abort_reason` field of the corresponding structure. The > > `jit.parse.finish()` returns now the second table containing aborted > > traces. Each table key is a trace number containing an array of > > potentially traces with this number, which was aborted. > > > > Needed for tarantool/tarantool#9924 > > --- > > .../unit-jit-parse-abort.test.lua | 38 +++++++++++++++++++ > > test/tarantool-tests/utils/jit/parse.lua | 22 ++++++++--- > > 2 files changed, 55 insertions(+), 5 deletions(-) > > create mode 100644 test/tarantool-tests/unit-jit-parse-abort.test.lua > > > > diff --git a/test/tarantool-tests/unit-jit-parse-abort.test.lua b/test/tarantool-tests/unit-jit-parse-abort.test.lua > > new file mode 100644 > > index 00000000..91af5a56 > > --- /dev/null > > +++ b/test/tarantool-tests/unit-jit-parse-abort.test.lua > > @@ -0,0 +1,38 @@ > > +local tap = require('tap') > > +local test = tap.test('unit-jit-parse'):skipcond({ > > Usually a name passed to `tap.test` matches to test file name, > > but here it is not matched. My bad, thanks! Fixed, see the iterative patch below. =================================================================== diff --git a/test/tarantool-tests/unit-jit-parse-abort.test.lua b/test/tarantool-tests/unit-jit-parse-abort.test.lua index 91af5a56..f09e696c 100644 --- a/test/tarantool-tests/unit-jit-parse-abort.test.lua +++ b/test/tarantool-tests/unit-jit-parse-abort.test.lua @@ -1,5 +1,5 @@ local tap = require('tap') -local test = tap.test('unit-jit-parse'):skipcond({ +local test = tap.test('unit-jit-parse-abort'):skipcond({ ['Test requires JIT enabled'] = not jit.status(), ['Disabled on *BSD due to #4819'] = jit.os == 'BSD', }) =================================================================== > > > + ['Test requires JIT enabled'] = not jit.status(), > > + ['Disabled on *BSD due to #4819'] = jit.os == 'BSD', > > +}) > > + > > +local jparse = require('utils').jit.parse > > + > > +-- XXX: Avoid other traces compilation due to hotcount collisions > > +-- for predictable results. > > +jit.off() > > +jit.flush() > > + > > +test:plan(1) > > + > > +jit.on() > > +-- We only need the abort reason in the test. > > +jparse.start('t') > > I would add a comment with explanation what does 't' flag mean. > > Feel free to ignore. I suppose that readers who use `jit.dump` from time to time already know all flags. If not, it can be easily found in <jit/dump.lua>. > > > + <snipped> > > -- Turn off compilation for the module to avoid side effects. -- Best regards, Sergey Kaplun
next prev parent reply other threads:[~2024-06-13 10:04 UTC|newest] Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-22 8:49 [Tarantool-patches] [PATCH luajit v1 0/5] Handle all errors during stitching Sergey Kaplun via Tarantool-patches 2024-04-22 8:49 ` [Tarantool-patches] [PATCH luajit v1 1/5] build: introduce option LUAJIT_ENABLE_TABLE_BUMP Sergey Kaplun via Tarantool-patches 2024-05-05 12:39 ` Maxim Kokryashkin via Tarantool-patches 2024-05-13 11:47 ` Sergey Kaplun via Tarantool-patches 2024-06-06 10:53 ` Sergey Bronnikov via Tarantool-patches 2024-06-13 9:51 ` Sergey Kaplun via Tarantool-patches 2024-06-13 14:37 ` Sergey Bronnikov via Tarantool-patches 2024-04-22 8:49 ` [Tarantool-patches] [PATCH luajit v1 2/5] ci: add tablebump flavor for exotic builds Sergey Kaplun via Tarantool-patches 2024-05-05 12:40 ` Maxim Kokryashkin via Tarantool-patches 2024-05-13 11:49 ` Sergey Kaplun via Tarantool-patches 2024-06-06 10:56 ` Sergey Bronnikov via Tarantool-patches 2024-04-22 8:49 ` [Tarantool-patches] [PATCH luajit v1 3/5] test: allow `jit.parse` to return aborted traces Sergey Kaplun via Tarantool-patches 2024-05-05 12:55 ` Maxim Kokryashkin via Tarantool-patches 2024-05-13 11:53 ` Sergey Kaplun via Tarantool-patches 2024-06-06 11:01 ` Sergey Bronnikov via Tarantool-patches 2024-06-13 10:00 ` Sergey Kaplun via Tarantool-patches [this message] 2024-06-13 14:38 ` Sergey Bronnikov via Tarantool-patches 2024-04-22 8:49 ` [Tarantool-patches] [PATCH luajit v1 4/5] Handle all types of errors during trace stitching Sergey Kaplun via Tarantool-patches 2024-05-06 8:25 ` Maxim Kokryashkin via Tarantool-patches 2024-06-06 13:03 ` Sergey Bronnikov via Tarantool-patches 2024-06-13 10:25 ` Sergey Kaplun via Tarantool-patches 2024-06-13 14:52 ` Sergey Bronnikov via Tarantool-patches 2024-04-22 8:49 ` [Tarantool-patches] [PATCH luajit v1 5/5] Use generic trace error for OOM " Sergey Kaplun via Tarantool-patches 2024-05-06 8:27 ` Maxim Kokryashkin via Tarantool-patches 2024-06-06 14:06 ` Sergey Bronnikov via Tarantool-patches 2024-06-13 10:31 ` Sergey Kaplun via Tarantool-patches 2024-06-13 14:58 ` Sergey Bronnikov via Tarantool-patches 2024-06-16 19:13 ` 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=ZmrDSzpiWgOgcZIb@root \ --to=tarantool-patches@dev.tarantool.org \ --cc=sergeyb@tarantool.org \ --cc=skaplun@tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH luajit v1 3/5] test: allow `jit.parse` to return aborted traces' \ /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