From: Alexander Turenko <alexander.turenko@tarantool.org> To: Artem Starshov <artemreyt@tarantool.org> Cc: tarantool-patches@dev.tarantool.org Subject: Re: [Tarantool-patches] [PATCH 3/3] test: new version for -e assert(false) test Date: Tue, 29 Dec 2020 23:16:35 +0300 [thread overview] Message-ID: <20201229201635.6jremx73yrtgnqdj@tkn_work_nb> (raw) In-Reply-To: <54be7a8eac0b6f9291e03b7f9ef26bbcc367e7b0.1609259010.git.artemreyt@tarantool.org> On Tue, Dec 29, 2020 at 07:25:35PM +0300, Artem Starshov wrote: > Functions with timeout transferred to module > test/app-tap/lua/process_timeout.lua for futher > using in other tests. Typo: futher -> further. > > Before this version of test was already done, > but by mistake older version was rebased on > master. BTW, I would mark all such commits as 'Follows up #4983'. It is a kind of grouping and may help to navigate over the history in a future. > -local fiber = require('fiber') > -local clock = require('clock') > -local ffi = require('ffi') > -local fio = require('fio') > -local errno = require('errno') > +local common = require('process_timeout') Why 'common', not 'process_timeout'? > diff --git a/test/app-tap/lua/process_timeout.lua b/test/app-tap/lua/process_timeout.lua > new file mode 100644 > index 000000000..141fb0e43 > --- /dev/null > +++ b/test/app-tap/lua/process_timeout.lua I would leave a comment that will describe a reason, why those functions are necessary in presence of the 'popen' built-in module.
next prev parent reply other threads:[~2020-12-29 20:16 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-29 16:25 [Tarantool-patches] [PATCH 0/3] test: -e assert(false) test fixup Artem Starshov 2020-12-29 16:25 ` [Tarantool-patches] [PATCH 1/3] test: tarantool -e test add more details and avoid busy loop Artem Starshov 2020-12-29 16:53 ` Leonid Vasiliev 2020-12-29 20:11 ` Alexander Turenko 2020-12-29 16:25 ` [Tarantool-patches] [PATCH 2/3] github-ci: add init option for containers Artem Starshov 2020-12-29 16:57 ` Leonid Vasiliev 2020-12-29 18:32 ` Alexander V. Tikhonov 2020-12-29 19:25 ` Alexander Turenko 2020-12-29 16:25 ` [Tarantool-patches] [PATCH 3/3] test: new version for -e assert(false) test Artem Starshov 2020-12-29 17:07 ` Leonid Vasiliev 2020-12-29 20:16 ` Alexander Turenko [this message] 2020-12-29 16:45 ` [Tarantool-patches] [PATCH 0/3] test: -e assert(false) test fixup Artem 2020-12-29 17:11 ` Leonid Vasiliev
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=20201229201635.6jremx73yrtgnqdj@tkn_work_nb \ --to=alexander.turenko@tarantool.org \ --cc=artemreyt@tarantool.org \ --cc=tarantool-patches@dev.tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH 3/3] test: new version for -e assert(false) test' \ /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