From: Cyrill Gorcunov <gorcunov@gmail.com> To: Vladislav Shpilevoy <v.shpilevoy@tarantool.org> Cc: tml <tarantool-patches@dev.tarantool.org> Subject: Re: [Tarantool-patches] [PATCH v2 4/4] qsync: don't send negative timeouts into fiber_cond_wait_timeout Date: Fri, 17 Jul 2020 23:33:36 +0300 [thread overview] Message-ID: <20200717203336.GB2613@grain> (raw) In-Reply-To: <a51bd1fd-aacd-7b1c-4001-f4acb4ea2183@tarantool.org> On Fri, Jul 17, 2020 at 10:03:49PM +0200, Vladislav Shpilevoy wrote: > > > > Am I missing something obvious here? > > I still don't see how to trigger this assert. Please, show a code sample with > error injection, if you think that will help. I explicitly added line > 'timeout = -1;' and all worked fine. > --- [cyrill@grain tarantool.git] git diff diff --git a/src/box/txn_limbo.c b/src/box/txn_limbo.c index 0924952b7..50e6326b3 100644 --- a/src/box/txn_limbo.c +++ b/src/box/txn_limbo.c @@ -175,8 +175,9 @@ txn_limbo_wait_complete(struct txn_limbo *limbo, struct txn_limbo_entry *entry) while (true) { double deadline = start_time + replication_synchro_timeout; double timeout = deadline - fiber_clock(); - if (timeout < 0) - goto do_rollback; + timeout = -1; + //if (timeout < 0) + // goto do_rollback; bool cancellable = fiber_set_cancellable(false); int rc = fiber_cond_wait_timeout(&limbo->wait_cond, timeout); fiber_set_cancellable(cancellable); @@ -512,8 +513,9 @@ txn_limbo_wait_confirm(struct txn_limbo *limbo) while (true) { double deadline = start_time + replication_synchro_timeout; double timeout = deadline - fiber_clock(); - if (timeout < 0) - goto timed_out; + timeout = -1; + //if (timeout < 0) + // goto timed_out; bool cancellable = fiber_set_cancellable(false); int rc = fiber_cond_wait_timeout(&limbo->wait_cond, timeout); fiber_set_cancellable(cancellable); --- [cyrill@grain test] ./test-run.py replication/qsync_basic.test.lua ... [001] [Instance "master" killed by signal: 6 (SIGABRT)] [001] Found assertion fail in the results file [/home/cyrill/d1/projects/tarantool/tarantool.git/test/var/001_replication/master.log]: You did the same thing? Note that it requires debug build.
next prev parent reply other threads:[~2020-07-17 20:33 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-14 14:44 [Tarantool-patches] [PATCH 0/4] qsync: continue cooking the code Cyrill Gorcunov 2020-07-14 14:44 ` [Tarantool-patches] [PATCH 1/4] qsync: add missing functions descriptions Cyrill Gorcunov 2020-07-14 14:44 ` [Tarantool-patches] [PATCH 2/4] qsync: drop txn_limbo_confirm_timeout Cyrill Gorcunov 2020-07-14 14:44 ` [Tarantool-patches] [PATCH 3/4] qsync: txn_limbo_wait_complete -- fix type conversion Cyrill Gorcunov 2020-07-14 14:44 ` [Tarantool-patches] [PATCH 4/4] qsync: don't send negative timeouts into fiber_cond_wait_timeout Cyrill Gorcunov 2020-07-14 14:53 ` [Tarantool-patches] [PATCH v2 " Cyrill Gorcunov 2020-07-16 22:45 ` Vladislav Shpilevoy 2020-07-17 7:25 ` Cyrill Gorcunov 2020-07-17 20:03 ` Vladislav Shpilevoy 2020-07-17 20:33 ` Cyrill Gorcunov [this message] 2020-07-17 20:43 ` Cyrill Gorcunov 2020-07-20 19:28 ` [Tarantool-patches] [PATCH 0/4] qsync: continue cooking the code Vladislav Shpilevoy
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=20200717203336.GB2613@grain \ --to=gorcunov@gmail.com \ --cc=tarantool-patches@dev.tarantool.org \ --cc=v.shpilevoy@tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH v2 4/4] qsync: don'\''t send negative timeouts into fiber_cond_wait_timeout' \ /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