From: Igor Munkin via Tarantool-patches <tarantool-patches@dev.tarantool.org> To: Sergey Kaplun <skaplun@tarantool.org> Cc: tarantool-patches@dev.tarantool.org Subject: Re: [Tarantool-patches] [PATCH v2 luajit 1/5] test: add lua-Harness test suite Date: Tue, 16 Mar 2021 00:06:19 +0300 [thread overview] Message-ID: <20210315210619.GI9042@tarantool.org> (raw) In-Reply-To: <20210315181028.GB16737@root> Sergey, On 15.03.21, Sergey Kaplun wrote: > Igor, > > Thanks for the review! > > On 15.03.21, Igor Munkin wrote: > > Sergey, > > > > Thanks for the patch! > > > > On 15.03.21, Sergey Kaplun wrote: <snipped> > > > diff --git a/test/CMakeLists.txt b/test/CMakeLists.txt > > > index 99471db..3a42f41 100644 > > > --- a/test/CMakeLists.txt > > > +++ b/test/CMakeLists.txt > > > @@ -43,10 +43,12 @@ endif() > > > set(LUAJIT_TEST_COMMAND "${LUAJIT_TEST_BINARY} -e dofile[[${LUAJIT_TEST_INIT}]]") > > > separate_arguments(LUAJIT_TEST_COMMAND) > > > > > > -add_subdirectory(tarantool-tests) > > > +add_subdirectory(lua-Harness-tests) > > > add_subdirectory(LuaJIT-tests) > > > +add_subdirectory(tarantool-tests) > > > > Why did you choose this order? > > Alphabetically, like in `ls` output. Feel free to propose your own. To conform the alphabetical sort order LuaJIT-tests directory should go before lua-Harness-tests directory. > <snipped> > > > diff --git a/test/lua-Harness-tests/CMakeLists.txt b/test/lua-Harness-tests/CMakeLists.txt > > > new file mode 100644 > > > index 0000000..9b35e5a > > > --- /dev/null > > > +++ b/test/lua-Harness-tests/CMakeLists.txt > > > @@ -0,0 +1,49 @@ > > > +# Test suite that has been added from lua-Harness test suite > > > +# in scope of https://github.com/tarantool/tarantool/issues/4473. > > > + > > > +# See the rationale in the root CMakeLists.txt > > > +cmake_minimum_required(VERSION 3.1 FATAL_ERROR) > > > + > > > +find_program(PROVE prove) > > > +if(NOT PROVE) > > > + message(WARNING "`prove' is not found, so lua-Harness-tests target is not generated") > > > + return() > > > +endif() > > > + > > > +set(LUA_TEST_FLAGS --failures --shuffle) > > > > Why did you drop TEST_DEPS variable containing the dependencies? > > Sorry, don't get it. What do you mean? If you look onto my iterative patch in the first review iteration, you'll find TEST_DEPS variable similar to the one in tarantool-tests CMakeLists.txt. I forgot to add it into CMakeLists.txt for LuaJIT-tests and remembered about it in this patch. > > > > > > +if(CMAKE_VERBOSE_MAKEFILE) > > > + list(APPEND LUA_TEST_FLAGS --verbose) > > > +endif() > > > + > > > +string(CONCAT LUA_PATH > > > + "./?.lua\;" > > > + "${CMAKE_CURRENT_SOURCE_DIR}/?.lua\;" > > > + "${LUAJIT_SOURCE_DIR}/?.lua\;" > > > +) > > > > There is not a word regarding such complex LUA_PATH configuration. > > Ok, it can be the one long string, but, in my opinion, this format is > more readable, plus, as a bonus, with it line length is less than 120 > characters. I'll join these lines into one if you insist. This is not the issue (and might be much better that my approach in tarantool-tests and I will patch the test runners to make it conform to one style later). I'm talking about the purpose for each entry. E.g. why do you need both "./?.lua" and "${CMAKE_CURRENT_SOURCE_DIR}/?.lua"? If you need "${LUAJIT_SOURCE_DIR}/?.lua" for jit.* modules, then why it's not required for other suites? Mention this explicitly, please. > > > > > > + > > > +string(CONCAT LUA_CPATH > > > + "./?${CMAKE_SHARED_LIBRARY_SUFFIX}\;" > > > + "${LUAJIT_SOURCE_DIR}/?${CMAKE_SHARED_LIBRARY_SUFFIX}\;" > > > +) > > > > Ditto. > > <snipped> > > > -- > > > 2.28.0 > > > > > > > -- > > Best regards, > > IM > > -- > Best regards, > Sergey Kaplun -- Best regards, IM
next prev parent reply other threads:[~2021-03-15 21:06 UTC|newest] Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-15 15:29 [Tarantool-patches] [PATCH v2 luajit 0/5] Adapt " Sergey Kaplun via Tarantool-patches 2021-03-15 15:29 ` [Tarantool-patches] [PATCH v2 luajit 1/5] test: add " Sergey Kaplun via Tarantool-patches 2021-03-15 17:37 ` Igor Munkin via Tarantool-patches 2021-03-15 18:10 ` Sergey Kaplun via Tarantool-patches 2021-03-15 21:06 ` Igor Munkin via Tarantool-patches [this message] 2021-03-16 9:38 ` Sergey Kaplun via Tarantool-patches 2021-03-16 11:08 ` Igor Munkin via Tarantool-patches 2021-03-16 12:02 ` Sergey Kaplun via Tarantool-patches 2021-03-16 13:50 ` Sergey Ostanevich via Tarantool-patches 2021-03-15 15:29 ` [Tarantool-patches] [PATCH v2 luajit 2/5] test: adjust lua-Harness suite for LuaJIT Sergey Kaplun via Tarantool-patches 2021-03-15 17:39 ` Igor Munkin via Tarantool-patches 2021-03-15 18:33 ` Sergey Kaplun via Tarantool-patches 2021-03-15 21:27 ` Igor Munkin via Tarantool-patches 2021-03-16 14:25 ` Sergey Ostanevich via Tarantool-patches 2021-03-15 15:29 ` [Tarantool-patches] [PATCH v2 luajit 3/5] test: adjust lua-Harness test suite for Tarantool Sergey Kaplun via Tarantool-patches 2021-03-15 17:44 ` Igor Munkin via Tarantool-patches 2021-03-16 6:01 ` Sergey Kaplun via Tarantool-patches 2021-03-16 10:51 ` Igor Munkin via Tarantool-patches 2021-03-16 14:51 ` Sergey Ostanevich via Tarantool-patches 2021-03-16 14:59 ` Sergey Kaplun via Tarantool-patches 2021-03-15 19:12 ` Igor Munkin via Tarantool-patches 2021-03-15 15:29 ` [Tarantool-patches] [PATCH v2 luajit 4/5] test: disable 241-standalone of lua-Harness suite Sergey Kaplun via Tarantool-patches 2021-03-16 14:51 ` Sergey Ostanevich via Tarantool-patches 2021-03-15 15:29 ` [Tarantool-patches] [PATCH v2 luajit 5/5] test: disable 411-luajit " Sergey Kaplun via Tarantool-patches 2021-03-16 14:52 ` Sergey Ostanevich via Tarantool-patches 2021-03-17 0:46 ` [Tarantool-patches] [PATCH v2 luajit 0/5] Adapt lua-Harness test suite Igor Munkin via Tarantool-patches 2021-03-17 7:32 ` Sergey Kaplun via Tarantool-patches 2021-03-17 10:27 ` Igor Munkin via Tarantool-patches 2021-03-17 10:31 ` Sergey Kaplun via Tarantool-patches 2021-03-17 16:49 ` Igor Munkin via Tarantool-patches
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=20210315210619.GI9042@tarantool.org \ --to=tarantool-patches@dev.tarantool.org \ --cc=imun@tarantool.org \ --cc=skaplun@tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH v2 luajit 1/5] test: add lua-Harness test 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