From: Vladislav Shpilevoy <v.shpilevoy@tarantool.org> To: sergos@tarantool.org, tarantool-patches@dev.tarantool.org Cc: alexander.turenko@tarantool.org Subject: Re: [Tarantool-patches] [PATCH v2] core: handle fiber cancellation for fiber.cond Date: Wed, 25 Nov 2020 22:32:59 +0100 [thread overview] Message-ID: <12e5f150-8e08-1004-ad8a-c6bd1a04fd5f@tarantool.org> (raw) In-Reply-To: <20201031162911.61876-1-sergos@tarantool.org> Hi! Thanks for the fixes! Technically the patch is good! See 3 non-technical comments below. > diff --git a/src/box/relay.cc b/src/box/relay.cc > index b68b45e00..a7bc2c6f7 100644 > --- a/src/box/relay.cc > +++ b/src/box/relay.cc > @@ -780,6 +771,16 @@ relay_subscribe_f(va_list ap) > cbus_endpoint_destroy(&relay->endpoint, cbus_process); > > relay_exit(relay); > + > + /* > + * Log the error that caused the relay to break the loop. > + * Don't clear the error for status reporting. > + */ > + assert(!diag_is_empty(&relay->diag)); > + diag_set_error(diag_get(), diag_last_error(&relay->diag)); > + diag_log(); > + say_crit("exiting the relay loop"); > + 1. I suggest you to move this to a separate commit, before you change fiber cond behaviour. Because it seems it is not related to conds really. And even if it would be related, still the issue looks like a separate bug. > return -1; > } > diff --git a/test/app-tap/gh-5013-fiber-cancel.test.lua b/test/app-tap/gh-5013-fiber-cancel.test.lua > new file mode 100755 > index 000000000..ca4ca2c90 > --- /dev/null > +++ b/test/app-tap/gh-5013-fiber-cancel.test.lua > @@ -0,0 +1,23 @@ > +#!/usr/bin/env tarantool > + > +local tap = require('tap') > +local fiber = require('fiber') > +local test = tap.test("gh-5013-fiber-cancel") > + > +test:plan(2) > + > +local result = {} > + > +function test_f() > + local cond = fiber.cond() > + local res, err = pcall(cond.wait, cond) > + result.res = res > + result.err = err > +end > + > +local f = fiber.create(test_f) > +f:cancel() > +fiber.yield() > + > +test:ok(result.res == false, 'expected result is false') > +test:ok(tostring(result.err) == 'fiber is cancelled', 'fiber cancellation should be reported') 2. I think you are also supposed to call os.exit with test:check() like other tap tests do. Otherwise it probably always ends with 0 code, and won't work properly when we will make tap tests non-diff based. > diff --git a/test/box/gh-4834-netbox-fiber-cancel.result b/test/box/gh-4834-netbox-fiber-cancel.result > new file mode 100644 > index 000000000..cb631995c > --- /dev/null > +++ b/test/box/gh-4834-netbox-fiber-cancel.result > @@ -0,0 +1,62 @@ > +-- test-run result file version 2 > +remote = require('net.box') > + | --- > + | ... > +fiber = require('fiber') > + | --- > + | ... > +test_run = require('test_run').new() > + | --- > + | ... > + > +-- #4834: Cancelling fiber doesn't interrupt netbox operations > +function infinite_call() fiber.channel(1):get() end 3. I noticed you never finish the fiber. So it hangs there forever or until a restart. Better not leave any test artifacts and finish it completely. Just save the channel to a global variable and put something into it in the end.
next prev parent reply other threads:[~2020-11-25 21:33 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-31 16:29 sergos 2020-11-01 10:13 ` Oleg Babin 2020-11-03 10:20 ` Sergey Ostanevich 2020-11-03 10:27 ` Oleg Babin 2020-11-04 10:00 ` Leonid Vasiliev 2020-11-16 22:12 ` Vladislav Shpilevoy 2020-11-18 22:05 ` Sergey Ostanevich 2020-11-22 16:01 ` Vladislav Shpilevoy 2020-11-23 21:47 ` Sergey Ostanevich 2020-11-24 7:31 ` Sergey Ostanevich 2020-11-04 10:00 ` Leonid Vasiliev 2020-11-05 20:42 ` Sergey Ostanevich 2020-11-10 21:16 ` Sergey Ostanevich 2020-11-12 20:15 ` Sergey Ostanevich 2020-11-13 8:26 ` Leonid Vasiliev 2020-11-30 22:49 ` Alexander Turenko 2020-11-16 22:12 ` Vladislav Shpilevoy 2020-11-25 21:32 ` Vladislav Shpilevoy [this message] 2020-11-29 21:41 ` Sergey Ostanevich 2020-11-30 21:46 ` Alexander Turenko 2020-11-30 21:01 ` Vladislav Shpilevoy 2020-12-02 10:58 ` Alexander V. Tikhonov 2020-12-02 22:18 ` 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=12e5f150-8e08-1004-ad8a-c6bd1a04fd5f@tarantool.org \ --to=v.shpilevoy@tarantool.org \ --cc=alexander.turenko@tarantool.org \ --cc=sergos@tarantool.org \ --cc=tarantool-patches@dev.tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH v2] core: handle fiber cancellation for fiber.cond' \ /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