From: Vladislav Shpilevoy via Tarantool-patches <tarantool-patches@dev.tarantool.org> To: imeevma@tarantool.org Cc: tarantool-patches@dev.tarantool.org Subject: Re: [Tarantool-patches] [PATCH v1 1/1] schema: remove assert on wrong insert into _priv Date: Tue, 7 Sep 2021 23:59:58 +0200 [thread overview] Message-ID: <4e091d79-84c5-9ba1-f624-185cfced6591@tarantool.org> (raw) In-Reply-To: <38ac1b8d1ecae3352b8fe748def9e8a451239b9a.1630915850.git.imeevma@gmail.com> Hi! Thanks for the patch! See 4 comments below. On 06.09.2021 10:11, imeevma@tarantool.org wrote: > Prior to this patch, an assertion was throwed if a tuple with an 1. throwed -> thrown. > incorrect id was inserted into the _priv system space. This bug > appeared only in the debug build. > > Closes #6295 > --- > https://github.com/tarantool/tarantool/issues/6295 > https://github.com/tarantool/tarantool/tree/imeevma/gh-6295-assert-on-insert-with-wrong-id 2. Could you please add a changelog? > diff --git a/test/box-tap/gh-6295-assert-on-wrong-id.test.lua b/test/box-tap/gh-6295-assert-on-wrong-id.test.lua > new file mode 100755 > index 000000000..e4822f395 > --- /dev/null > +++ b/test/box-tap/gh-6295-assert-on-wrong-id.test.lua > @@ -0,0 +1,34 @@ > +#!/usr/bin/env tarantool > + > +local tap = require('tap') > +local test = tap.test('gh-6295-assert-on-wrong-id') > + > +test:plan(5) > + > +local ok, res > + > +box.cfg{} > + > +-- Should be an error, not an assertion. > +local _priv = box.space._priv > +local errmsg = "Function '1000000' does not exist" > +ok, res = pcall(_priv.replace, _priv, {1, 2, 'function', 1000000, box.priv.A}) > +test:is_deeply({ok, tostring(res)}, {false, errmsg}, "Function exists") 3. Shouldn't the message be like a comment? Describing the correct behaviour. It is printed always along with ok/no ok in the tap output. So it should be about what is expected. > diff --git a/test/box-tap/suite.ini b/test/box-tap/suite.ini > index b09d7db4f..fd55d5d24 100644 > --- a/test/box-tap/suite.ini > +++ b/test/box-tap/suite.ini > @@ -3,7 +3,7 @@ core = app > description = Database tests with #! using TAP > is_parallel = True > use_unix_sockets_iproto = True > -release_disabled = errinj_set_with_enviroment_vars.test.lua > +release_disabled = errinj_set_with_enviroment_vars.test.lua, gh-6295-assert-on-wrong-id.test.lua 4. Why? The test does not pass in release? > config = suite.cfg > fragile = { > "retries": 10, >
next prev parent reply other threads:[~2021-09-07 22:00 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-09-06 8:11 Mergen Imeev via Tarantool-patches 2021-09-07 21:59 ` Vladislav Shpilevoy via Tarantool-patches [this message] 2021-09-09 11:07 ` Mergen Imeev via Tarantool-patches 2021-09-27 6:41 ` Mergen Imeev via Tarantool-patches 2021-09-27 22:33 ` Vladislav Shpilevoy via Tarantool-patches 2021-09-29 6:32 ` Mergen Imeev via Tarantool-patches 2021-09-30 22:46 ` Vladislav Shpilevoy via Tarantool-patches 2021-10-05 12:13 ` Kirill Yukhin via Tarantool-patches -- strict thread matches above, loose matches on Subject: below -- 2021-08-16 16:13 Mergen Imeev via Tarantool-patches 2021-08-17 12:32 ` Serge Petrenko via Tarantool-patches 2021-09-03 6:59 ` Mergen Imeev via Tarantool-patches 2021-09-06 8:05 ` Serge Petrenko 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=4e091d79-84c5-9ba1-f624-185cfced6591@tarantool.org \ --to=tarantool-patches@dev.tarantool.org \ --cc=imeevma@tarantool.org \ --cc=v.shpilevoy@tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH v1 1/1] schema: remove assert on wrong insert into _priv' \ /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