From: Igor Munkin via Tarantool-patches <tarantool-patches@dev.tarantool.org> To: Sergey Kaplun <skaplun@tarantool.org>, Timur Safin <tsafin@tarantool.org> Cc: tarantool-patches@dev.tarantool.org Subject: Re: [Tarantool-patches] [PATCH luajit 0/5] Self-sufficient LuaJIT testing environment Date: Mon, 1 Mar 2021 01:04:04 +0300 [thread overview] Message-ID: <20210228220404.GI9042@tarantool.org> (raw) In-Reply-To: <cover.1612291495.git.imun@tarantool.org> I've checked the patchset into all long-term branches in tarantool/luajit and bumped a new version in 1.10, 2.6, 2.7 and master. NB: there is no separate commit with submodule bump, since there are many change in LuaJIT build system in Tarantool repo too. For more info see this series[1]. On 02.02.21, Igor Munkin wrote: > This series moves LuaJIT-related parts of Tarantool testing machinery to > LuaJIT repository. For this purpose the build system is partially ported > to CMake. To avoid Makefiles name clashing the original build system is > renamed to keep it working. As a result of these changes one need to > explicitly specify the Makefile in the build command: > | make -f Makefile.original <options> > > These changes provides CMake build system only for the following OS: > GNU/Linux, OSX, FreeBSD. For other platrforms use the old build system. > > To run all available tests a separate target is introduced. The whole > testing machinery is reworked much but the existing tests are left > mostly unchanged. However, considering the way LuaJIT is integrated > into Tarantool, this machinery provides two new configuration options: > * LUAJIT_USE_TEST: to omit <test> target configuration for LuaJIT to > respect CMP0002 policy. > * LUAJIT_TEST_BINARY: to choose which binary (i.e. Lua runtime) to be > used for running them. > > The latter option value is used as a dependency for tests, and its > default value is $<TARGET_FILE:${LUAJIT_DEPS}>. Unfortunately older > CMake can't expand the generator expression used in DEPENDS section of > <add_custom_(command|target)>. As a result the CMake minimum required > version is bumped to 3.1 project-wide[1]. For more info see CMake Release > notes[2] for 3.1 version. > > Finally, existing tests are grouped and moved to a separate directory > under the root test directory to make the further addition of other > available test suites in scope of #4064[3] and #4473[4] easier. > > Tarantool tests are implemented using Tarantool on-board TAP module[5], > that is moved to LuaJIT repository with a little changes to save Lua > chunks untouched. Other auxiliary files for Tarantool-specific testing > (such as *.skipcond, suite.ini), in turn, are removed. > > To run static analysis for Lua chunks a separate target is introduced. > In scope of this target luacheck is run against all Lua chunks within > LuaJIT repository except those inherited from LuaJIT vanilla repository, > to leave them coherent with the upstream. > > Since the regular static analysis has not been enabled for the test > chunks in LuaJIT repository yet, the tests for recently implemented > features still produce luacheck warnings. The most of the issues are > fixed in scope of the commit 8fc103fb1a21c28185a1942e75d8d9485e3aade7 > ('test: fix warnings spotted by luacheck') and the last patch fixes the > remaining ones. > > [1]: https://lists.tarantool.org/tarantool-patches/20210127130947.yw5sdswpokujblyr@tarantool.org/T/#t > [2]: https://cmake.org/cmake/help/latest/release/3.1.html#commands > [3]: https://github.com/tarantool/tarantool/issues/4064 > [4]: https://github.com/tarantool/tarantool/issues/4473 > [5]: https://www.tarantool.io/en/doc/latest/reference/reference_lua/tap/ > > Branch: https://github.com/tarantool/luajit/tree/imun/gh-4862-cmake > Issues: > * https://github.com/tarantool/tarantool/issues/4862 > * https://github.com/tarantool/tarantool/issues/5470 > * https://github.com/tarantool/tarantool/issues/5631 > > Igor Munkin (5): > build: preserve the original build system > build: replace GNU Make with CMake > test: run LuaJIT tests via CMake > test: fix warnings found with luacheck in misclib* > test: run luacheck static analysis via CMake > <snipped> > > -- > 2.25.0 > [1]: https://lists.tarantool.org/tarantool-patches/20210227135610.GD6842@root/T/#t -- Best regards, IM
prev parent reply other threads:[~2021-02-28 22:04 UTC|newest] Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-02 20:57 Igor Munkin via Tarantool-patches 2021-02-02 20:57 ` [Tarantool-patches] [PATCH luajit 1/5] build: preserve the original build system Igor Munkin via Tarantool-patches 2021-02-04 22:53 ` Timur Safin via Tarantool-patches 2021-02-08 15:56 ` Igor Munkin via Tarantool-patches 2021-02-09 11:38 ` Sergey Kaplun via Tarantool-patches 2021-02-09 12:47 ` Igor Munkin via Tarantool-patches 2021-02-09 14:45 ` Sergey Kaplun via Tarantool-patches 2021-02-09 15:28 ` Igor Munkin via Tarantool-patches 2021-02-10 9:35 ` Sergey Kaplun via Tarantool-patches 2021-02-02 20:57 ` [Tarantool-patches] [PATCH luajit 2/5] build: replace GNU Make with CMake Igor Munkin via Tarantool-patches 2021-02-04 22:53 ` Timur Safin via Tarantool-patches 2021-02-08 15:56 ` Igor Munkin via Tarantool-patches 2021-02-09 13:55 ` Timur Safin via Tarantool-patches 2021-02-09 15:09 ` Igor Munkin via Tarantool-patches 2021-02-11 19:23 ` Sergey Kaplun via Tarantool-patches 2021-02-16 15:28 ` Igor Munkin via Tarantool-patches 2021-02-18 9:56 ` Sergey Kaplun via Tarantool-patches 2021-02-20 19:18 ` Igor Munkin via Tarantool-patches 2021-02-27 10:48 ` Sergey Kaplun via Tarantool-patches 2021-02-28 18:18 ` Igor Munkin via Tarantool-patches 2021-02-13 3:47 ` Sergey Kaplun via Tarantool-patches 2021-02-16 15:32 ` Igor Munkin via Tarantool-patches 2021-02-02 20:57 ` [Tarantool-patches] [PATCH luajit 3/5] test: run LuaJIT tests via CMake Igor Munkin via Tarantool-patches 2021-02-08 15:05 ` Timur Safin via Tarantool-patches 2021-02-08 16:29 ` Igor Munkin via Tarantool-patches 2021-02-09 8:16 ` Timur Safin via Tarantool-patches 2021-02-09 8:43 ` Igor Munkin via Tarantool-patches 2021-02-09 13:59 ` Timur Safin via Tarantool-patches 2021-02-09 15:10 ` Igor Munkin via Tarantool-patches 2021-02-14 18:48 ` Sergey Kaplun via Tarantool-patches 2021-02-19 19:04 ` Igor Munkin via Tarantool-patches 2021-02-27 13:50 ` Sergey Kaplun via Tarantool-patches 2021-02-28 18:18 ` Igor Munkin via Tarantool-patches 2021-02-02 20:57 ` [Tarantool-patches] [PATCH luajit 4/5] test: fix warnings found with luacheck in misclib* Igor Munkin via Tarantool-patches [not found] ` <012f01d6fe1a$a2aa6890$e7ff39b0$@tarantool.org> 2021-02-08 15:57 ` Igor Munkin via Tarantool-patches [not found] ` <2c495492-50f4-acfd-ad66-2cb44abb5fa1@tarantool.org> 2021-02-08 15:40 ` Sergey Bronnikov via Tarantool-patches 2021-02-08 15:58 ` Igor Munkin via Tarantool-patches 2021-02-14 19:16 ` Sergey Kaplun via Tarantool-patches 2021-02-16 15:29 ` Igor Munkin via Tarantool-patches 2021-02-16 16:36 ` Sergey Kaplun via Tarantool-patches 2021-02-02 20:57 ` [Tarantool-patches] [PATCH luajit 5/5] test: run luacheck static analysis via CMake Igor Munkin via Tarantool-patches 2021-02-04 22:52 ` Timur Safin via Tarantool-patches 2021-02-08 15:57 ` Igor Munkin via Tarantool-patches 2021-02-14 19:32 ` Sergey Kaplun via Tarantool-patches 2021-02-19 19:14 ` Igor Munkin via Tarantool-patches 2021-02-28 22:04 ` Igor Munkin via Tarantool-patches [this message]
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=20210228220404.GI9042@tarantool.org \ --to=tarantool-patches@dev.tarantool.org \ --cc=imun@tarantool.org \ --cc=skaplun@tarantool.org \ --cc=tsafin@tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH luajit 0/5] Self-sufficient LuaJIT testing environment' \ /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