From: Sergey Bronnikov <sergeyb@tarantool.org> To: Vladislav Shpilevoy <v.shpilevoy@tarantool.org> Cc: o.piskunov@tarantool.org, Sergey Bronnikov <estetus@gmail.com>, tarantool-patches@dev.tarantool.org Subject: Re: [Tarantool-patches] [PATCH v2 5/6] Add luacheck config Date: Wed, 15 Apr 2020 11:30:02 +0300 [thread overview] Message-ID: <20200415083002.GB40826@pony.bronevichok.ru> (raw) In-Reply-To: <c118db17-404b-db67-fed4-ceea20ac0a2d@tarantool.org> Hi, Vladislav, see comments inline. On 01:29 Wed 15 Apr , Vladislav Shpilevoy wrote: > Hi! Thanks for the answer! > > >>> Lua source code in test/ directory contains both errors and warnings and there > >>> are a lot of them. Some of these warnings were fixed by previous commits and > >>> most part of warnings and errors supressed in luacheck config. Regarding > >>> errors: all found errors belongs to a single error class - "Syntax error" > >>> (E011). All of them have a single root cause - at the of testscases we write > >>> conditions without assignments and it is confuses luacheck. Usually such > >>> conditions used together with asserts, but in our tests we uses reference outputs > >>> instead of asserts. > >> > >> 1. So you disabled that warning for tests, right? Then why still many > >> statements in the test/ dir are replaced with assertions in one of the > >> previous commits? > > > > My original goal was following: fix dangerous warnings and supress other > > of them per file. I followed this strategy and then discovered that E011 > > cannot be supressed. In case of errors you should fix them or disable > > checking at all for highlighted files/directories. So this is a reason > > why some exclusions contains single file and some of them contains file > > mask. I decided to keep it as is because more specific supressions are > > more convenient to fix when. > > I still think, that if a whole folder was ignored in exclude_files, then > it does not make sense to add individual files from this folder again. > Anyway we won't be able to maintain warning ignorance for these files, > because they are just invisible for luacheck. Got it. > But I will leave it to a second reviewer. Igor wanted to take a look too. Well, I'll wait Igor and then update patchset accordingly. S.
next prev parent reply other threads:[~2020-04-15 8:30 UTC|newest] Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-04-08 15:42 [Tarantool-patches] [PATCH v2 0/6] Add static analysis with luacheck Sergey Bronnikov 2020-04-08 15:43 ` [Tarantool-patches] [PATCH v2 1/6] Fix luacheck warnings in src/lua/ Sergey Bronnikov 2020-04-09 4:31 ` Alexander Tikhonov 2020-04-11 16:54 ` Vladislav Shpilevoy 2020-04-08 15:43 ` [Tarantool-patches] [PATCH v2 2/6] Fix luacheck warnings in test/ Sergey Bronnikov 2020-04-09 4:31 ` Alexander Tikhonov 2020-04-11 16:54 ` Vladislav Shpilevoy 2020-04-14 7:49 ` Sergey Bronnikov 2020-04-11 16:54 ` Vladislav Shpilevoy 2020-04-08 15:43 ` [Tarantool-patches] [PATCH v2 3/6] Fix luacheck warnings in src/box/lua/ Sergey Bronnikov 2020-04-09 4:29 ` Alexander Tikhonov 2020-04-08 15:43 ` [Tarantool-patches] [PATCH v2 4/6] Fix luacheck warnings in extra/dist/tarantoolctl.in Sergey Bronnikov 2020-04-09 4:29 ` Alexander Tikhonov 2020-04-09 7:30 ` Oleg Babin 2020-04-10 14:05 ` Sergey Bronnikov 2020-04-15 15:14 ` Igor Munkin 2020-04-15 15:37 ` Igor Munkin 2020-04-08 15:43 ` [Tarantool-patches] [PATCH v2 5/6] Add luacheck config Sergey Bronnikov 2020-04-09 4:27 ` Alexander Tikhonov 2020-04-11 16:54 ` Vladislav Shpilevoy 2020-04-13 15:16 ` Sergey Bronnikov 2020-04-14 23:29 ` Vladislav Shpilevoy 2020-04-15 8:30 ` Sergey Bronnikov [this message] 2020-04-08 15:43 ` [Tarantool-patches] [PATCH v2 6/6] gitlab-ci: enable static analysis with luacheck Sergey Bronnikov 2020-04-09 4:20 ` Alexander Tikhonov 2020-04-10 14:53 ` Sergey Bronnikov 2020-04-22 8:45 ` Alexander Tikhonov
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=20200415083002.GB40826@pony.bronevichok.ru \ --to=sergeyb@tarantool.org \ --cc=estetus@gmail.com \ --cc=o.piskunov@tarantool.org \ --cc=tarantool-patches@dev.tarantool.org \ --cc=v.shpilevoy@tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH v2 5/6] Add luacheck config' \ /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