From: Alexander Turenko <alexander.turenko@tarantool.org>
To: avtikhon <avtikhon@tarantool.org>
Cc: tarantool-patches@freelists.org
Subject: [tarantool-patches] Re: [PATCH v1] test: enable parallel testing for vinyl suite
Date: Mon, 15 Apr 2019 16:25:54 +0300 [thread overview]
Message-ID: <20190415132554.vxxxuiex3owtk2it@tkn_work_nb> (raw)
In-Reply-To: <836868d9fe292582c3dbc7ade8919081686fee22.1555329875.git.avtikhon@tarantool.org>
I have enabled core files: ulimit -c unlimited.
Then I run:
for i in $(seq 1 100); do ./test-run.py -j 30 --long vinyl/ || break; done
And observed the following crash:
[020] [Instance "low_quota" killed by signal: 11 (SIGSEGV)]
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x000055ec89ca3e04 in matras_view_get_no_check (m=0x55ec8ae6eda8, v=0x55ec8af64080, id=0) at /home/alex/p/tarantool-meta/tarantool/src/lib/small/small/matras.h:353
353 return &extent[n1][n2][n3 * m->block_size];
[Current thread is 1 (Thread 0x7f7444bff700 (LWP 3114))]
(gdb) bt
#0 0x000055ec89ca3e04 in matras_view_get_no_check (m=0x55ec8ae6eda8, v=0x55ec8af64080, id=0) at /home/alex/p/tarantool-meta/tarantool/src/lib/small/small/matras.h:353
#1 0x000055ec89ca3e62 in matras_view_get (m=0x55ec8ae6eda8, v=0x55ec8af64080, id=0) at /home/alex/p/tarantool-meta/tarantool/src/lib/small/small/matras.h:363
#2 0x000055ec89ca4762 in bps_tree_memtx_tree_restore_block_ver (tree=0x55ec8ae6ed60, id=0, view=0x55ec8af64080) at /home/alex/p/tarantool-meta/tarantool/src/lib/salad/bps_tree.h:1285
#3 0x000055ec89ca4d55 in bps_tree_memtx_tree_get_leaf_safe (tree=0x55ec8ae6ed60, itr=0x55ec8af64078) at /home/alex/p/tarantool-meta/tarantool/src/lib/salad/bps_tree.h:1552
#4 0x000055ec89ca5763 in memtx_tree_iterator_get_elem (tree=0x55ec8ae6ed60, itr=0x55ec8af64078) at /home/alex/p/tarantool-meta/tarantool/src/lib/salad/bps_tree.h:1970
#5 0x000055ec89caedfd in tree_snapshot_iterator_next (iterator=0x55ec8af64060, size=0x7f74454fe61c) at /home/alex/p/tarantool-meta/tarantool/src/box/memtx_tree.c:734
#6 0x000055ec89cb6e66 in checkpoint_f (ap=0x7f7445400228) at /home/alex/p/tarantool-meta/tarantool/src/box/memtx_engine.c:661
#7 0x000055ec89c8f9a9 in fiber_cxx_invoke(fiber_func, typedef __va_list_tag __va_list_tag *) (f=0x55ec89cb6ce6 <checkpoint_f>, ap=0x7f7445400228)
at /home/alex/p/tarantool-meta/tarantool/src/lib/core/fiber.h:672
#8 0x000055ec89db5b73 in fiber_loop (data=0x0) at /home/alex/p/tarantool-meta/tarantool/src/lib/core/fiber.c:694
#9 0x000055ec89f8ccb3 in coro_init () at /home/alex/p/tarantool-meta/tarantool/third_party/coro/coro.c:110
2.2.0-179-ga00169714.
Also I found a bunch of open issues re vinyl in parallel mode, added to
#4158. Please, resolve them first.
WBR, Alexander Turenko.
On Mon, Apr 15, 2019 at 03:06:44PM +0300, avtikhon wrote:
> Need to switch on is_parallel flag for vinyl suite
> to be able to run subtests in parallel using:
> ./test_run.pl -j'<threads>'
>
> Close #4158
> ---
>
> Github: https://github.com/tarantool/tarantool/tree/avtikhon/gh4158-vinyl-parallel
> Issue: https://github.com/tarantool/tarantool/issues/4158
>
> test/vinyl/suite.ini | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/test/vinyl/suite.ini b/test/vinyl/suite.ini
> index 3612cf44b..98d9eb5ae 100644
> --- a/test/vinyl/suite.ini
> +++ b/test/vinyl/suite.ini
> @@ -7,6 +7,6 @@ config = suite.cfg
> lua_libs = suite.lua stress.lua large.lua txn_proxy.lua ../box/lua/utils.lua
> use_unix_sockets = True
> long_run = stress.test.lua large.test.lua write_iterator_rand.test.lua dump_stress.test.lua select_consistency.test.lua throttle.test.lua
> -is_parallel = False
> +is_parallel = True
> disabled = upgrade.test.lua
> pretest_clean = True
> --
> 2.17.1
>
prev parent reply other threads:[~2019-04-15 13:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-15 12:06 [tarantool-patches] " avtikhon
2019-04-15 13:25 ` Alexander Turenko [this message]
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=20190415132554.vxxxuiex3owtk2it@tkn_work_nb \
--to=alexander.turenko@tarantool.org \
--cc=avtikhon@tarantool.org \
--cc=tarantool-patches@freelists.org \
--subject='[tarantool-patches] Re: [PATCH v1] test: enable parallel testing for vinyl suite' \
/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