From: Sergey Bronnikov <sergeyb@tarantool.org>
To: Alexander Turenko <alexander.turenko@tarantool.org>
Cc: Mons Anderson <v.perepelitsa@corp.mail.ru>,
tarantool-patches@dev.tarantool.org,
Vladislav Shpilevoy <v.shpilevoy@tarantool.org>
Subject: Re: [Tarantool-patches] [PATCH] Add options for upgrade testing
Date: Wed, 2 Dec 2020 13:49:39 +0300 [thread overview]
Message-ID: <fb3e9448-9d05-e1c0-264c-27479bd24719@tarantool.org> (raw)
In-Reply-To: <20201202034003.mezalnkxy3pwyecp@tkn_work_nb>
On 02.12.2020 06:40, Alexander Turenko wrote:
<snipped>
> I'm okay with the state on the branch [3] (it is updated as shown above)
> and I ready to push it if you don't have objections against the result
> of squashing. I included my variant of extract_schema_from_snapshot()
> (but it leans on PATH, it is enough for usages from TarantoolServer).
I have tested patches again and it seems it works as expected.
Let's merge patches to master.
>
> I performed the following tests using tarantool 2.7.0-73-gb53cb2aec
> repository (debug build).
>
> 0. make lint
> No errors / warnings. Okay.
>
> 1. An app test.
> | (cd test && ./test-run.py box-tap/merger.test.lua)
> Passed. Okay.
>
> 2. An app test. Snapshot from 1.10.
> | (cd test && ./test-run.py \
> | --snapshot ../../../1.10/00000000000000000000.snap \
> | box-tap/merger.test.lua)
> Passed. Upgrade entries are present in the log. Okay.
>
> 3. An app test. Snapshot from 1.10. No schema upgrade.
> | (cd test && ./test-run.py \
> | --snapshot ../../../1.10/00000000000000000000.snap \
> | box-tap/merger.test.lua --disable-schema-upgrade)
> Passed. No upgrade entries in the log. Okay.
>
> 4. A tarantool test.
> | (cd test && ./test-run.py box/net.box_timeout_gh-1533.test.lua)
> Passed. Okay.
>
> 5. A tarantool test. Snapshot from 1.10.
> | (cd test && ./test-run.py \
> | --snapshot ../../../1.10/00000000000000000000.snap \
> | box/net.box_timeout_gh-1533.test.lua)
> Passed. Upgrade entries are present in the log. Okay.
>
> 6. A tarantool test. Snapshot from 1.10. No schema upgrade.
> | (cd test && ./test-run.py \
> | --snapshot ../../../1.10/00000000000000000000.snap \
> | box/net.box_timeout_gh-1533.test.lua --disable-schema-upgrade)
> Passed. No upgrade entries in the log. Okay.
>
> 7. --disable-schema-upgrade without --snapshot.
> | (cd test && ./test-run.py --disable-schema-upgrade)
> Gives an error. Okay.
>
> 8. Conflicting options.
> | (cd test && ./test-run.py --gdb --valgrind)
> Gives an error. Okay.
>
> 9. Run the whole test suite.
> | (cd test && ./test-run.py --long --force)
> Passed except replication/election_qsync_stress.test.lua, which is
> known as flaky on this revision. Okay.
>
> Rebuilt the same tarantool revision as RelWithDebInfo and performed the
> following test:
>
> 10. Attempt to use --disable-schema-upgrade on a RelWithDebInfo build.
> | (cd test && ./test-run.py \
> | --snapshot ../../../1.10/00000000000000000000.snap \
> | box/net.box_timeout_gh-1533.test.lua --disable-schema-upgrade)
> Gives an error. Okay.
>
> I rewrote my 'snapshot mangling' patches to introduce the new
> --bootstrap option and pushed them to the branch [4]. I propose to don't
> push them to master at least until we'll found them useful.
>
> [1]: https://github.com/tarantool/tarantool/issues/5540
> [2]: https://github.com/tarantool/tarantool/issues/4801
> [3]: ligurio/gh-4801-add-snapshot-option
> [4]: Totktonada/gh-4801-add-bootstrap-option
next prev parent reply other threads:[~2020-12-02 10:49 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-30 14:48 [Tarantool-patches] [test-run] " Sergey Bronnikov
2020-05-15 16:17 ` Alexander Turenko
2020-05-28 9:39 ` Sergey Bronnikov
2020-06-02 11:13 ` Alexander Turenko
2020-06-10 11:29 ` Sergey Bronnikov
2020-11-10 9:55 ` Sergey Bronnikov
2020-11-13 12:41 ` Leonid Vasiliev
2020-11-19 9:44 ` Sergey Bronnikov
2020-11-16 16:40 ` Alexander Turenko
2020-11-18 9:18 ` Sergey Bronnikov
2020-11-18 9:33 ` Sergey Bronnikov
2020-11-18 9:30 ` [Tarantool-patches] [PATCH] " sergeyb
2020-11-19 22:58 ` Alexander Turenko
2020-11-20 19:27 ` Sergey Bronnikov
2020-11-27 1:45 ` Alexander Turenko
2020-12-01 12:32 ` Sergey Bronnikov
2020-12-02 3:40 ` Alexander Turenko
2020-12-02 10:49 ` Sergey Bronnikov [this message]
2020-12-03 2:09 ` Alexander Turenko
2020-12-04 4:08 ` Alexander Turenko
2020-11-29 1:54 ` Alexander Turenko
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=fb3e9448-9d05-e1c0-264c-27479bd24719@tarantool.org \
--to=sergeyb@tarantool.org \
--cc=alexander.turenko@tarantool.org \
--cc=tarantool-patches@dev.tarantool.org \
--cc=v.perepelitsa@corp.mail.ru \
--cc=v.shpilevoy@tarantool.org \
--subject='Re: [Tarantool-patches] [PATCH] Add options for upgrade testing' \
/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