Tarantool development patches archive
 help / color / mirror / Atom feed
From: Alexander Turenko <alexander.turenko@tarantool.org>
To: Sergey Bronnikov <sergeyb@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: Fri, 4 Dec 2020 07:08:45 +0300	[thread overview]
Message-ID: <20201204040845.reiyxvyqa3voyn7u@tkn_work_nb> (raw)
In-Reply-To: <20201203020918.ocbocxnkzgardnuz@tkn_work_nb>

Alexander said he doesn't have objections.

Updated the test-run submodule in 2.7.0-81-gaf0e365e2,
2.6.1-68-g84b4f3314, 2.5.2-42-g28ef5bc44, 1.10.8-29-g024f078db.

WBR, Alexander Turenko.

On Thu, Dec 03, 2020 at 05:09:19AM +0300, Alexander Turenko wrote:
> On Wed, Dec 02, 2020 at 01:49:39PM +0300, Sergey Bronnikov wrote:
> > 
> > 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.
> 
> Nice.
> 
> Fixed a typo:
> 
>  | diff --git a/lib/options.py b/lib/options.py
>  | index bd3adc7..445d0d9 100644
>  | --- a/lib/options.py
>  | +++ b/lib/options.py
>  | @@ -256,7 +256,7 @@ class Options:
>  |              check_error = True
>  | 
>  |          if snapshot_path and not os.path.exists(snapshot_path):
>  | -            color_stdout("\nPath {} not exists\n".format(snapshot_path), schema='error')
>  | +            color_stdout("\nPath {} does not exist\n".format(snapshot_path), schema='error')
>  |              check_error = True
>  | 
>  |          if check_error:
> 
> Pushed to master of the test-run repository.
> 
> Alexander, I need your approve to push the corresponding submodule
> update into tarantool. Please, take in at a glance. I pushed the update
> into the [1] branch to trigger CI, for your convenience.
> 
> [1]: Totktonada/test-run-snapshot-cli-option
> 
> The commit itself:
> 
> commit b27ebb49e173a23259be73d8808b204efda3be03
> Author: Alexander Turenko <alexander.turenko@tarantool.org>
> Date:   Wed Dec 2 22:17:08 2020 +0300
> 
>     test: update test-run (--snapshot)
>     
>     * Added --snapshot and --disable-schema-upgrade arguments (#240).
>     * Fixed reporting of an error for conflicting arguments (#241).
>     
>     The `--snapshot path/to/snapshot` argument copies a given snapshot to a
>     snapshot directory before start a tarantool instance. This allows to
>     verify various functionality in the case, when tarantool is upgraded
>     from a snapshot that is left by an older tarantool version (as opposite
>     to test it on a freshly bootstrapped instance). There are limitations:
>     when a test spawns a replica set, the option does not work correctly.
>     The reason is that the same instance UUIDs (and IDs) cannot be used by
>     different instances in a replica set. Maybe there are other pitfalls.
>     
>     The `--disable-schema-upgrade` argument instructs tarantool to skip
>     execution of the schema upgrade script (using ERRINJ_AUTO_UPGRADE). This
>     way we can verify that, when an instance works on an old schema version,
>     a functionality is workable or at least gives correct error message.
>     
>     This commit only brings the new options into test-run. It does NOT add
>     any new testing targets / rules.
>     
>     Part of #4801
> 
> diff --git a/test-run b/test-run
> index 08a4817bc..26aa3875a 160000
> --- a/test-run
> +++ b/test-run
> @@ -1 +1 @@
> -Subproject commit 08a4817bc85ac162a60fa26e943d7485a6fb2a6c
> +Subproject commit 26aa3875a7a51952cdb9f487c0e14bbef380db0c

  reply	other threads:[~2020-12-04  4:08 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
2020-12-03  2:09                       ` Alexander Turenko
2020-12-04  4:08                         ` Alexander Turenko [this message]
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=20201204040845.reiyxvyqa3voyn7u@tkn_work_nb \
    --to=alexander.turenko@tarantool.org \
    --cc=sergeyb@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