From: Sergey Bronnikov via Tarantool-patches <tarantool-patches@dev.tarantool.org> To: tarantool-patches@dev.tarantool.org, Sergey Kaplun <skaplun@tarantool.org>, Maxim Kokryashkin <m.kokryashkin@tarantool.org> Subject: [Tarantool-patches] [PATCH luajit 0/6][v5] cmake: replace prove with CTest Date: Tue, 26 Mar 2024 11:33:26 +0300 [thread overview] Message-ID: <cover.1711441864.git.sergeyb@tarantool.org> (raw) From: Sergey Bronnikov <sergeyb@tarantool.org> Changes v5: - applied fixes suggested by Sergey Kaplun - added patches with prerequisites PR: https://github.com/tarantool/tarantool/pull/9286 Branch: https://github.com/tarantool/luajit/tree/ligurio/enable_test_target Sergey Bronnikov (4): ci: execute LuaJIT tests with GCC 10 and ASAN test: refactor CMake macro LibRealPath test: more cautious usage of LD_PRELOAD for ASan cmake: replace prove with CTest Sergey Kaplun (2): test: move LibRealPath to the separate module test: fix lj-802-panic-at-mcode-protfail GCC+ASan .github/actions/setup-sanitizers/action.yml | 15 ++- .github/workflows/sanitizers-testing.yml | 4 + .gitignore | 2 + CMakeLists.txt | 14 +++ test/CMakeLists.txt | 108 +++++++++++++++----- test/LuaJIT-tests/CMakeLists.txt | 61 +++++------ test/PUC-Rio-Lua-5.1-tests/CMakeLists.txt | 25 +++-- test/cmake/LibRealPath.cmake | 41 ++++++++ test/lua-Harness-tests/CMakeLists.txt | 50 +++++---- test/tarantool-c-tests/CMakeLists.txt | 58 +++++------ test/tarantool-tests/CMakeLists.txt | 77 ++++++++------ test/tarantool-tests/utils/exec.lua | 14 +++ 12 files changed, 320 insertions(+), 149 deletions(-) create mode 100644 test/cmake/LibRealPath.cmake -- 2.34.1
next reply other threads:[~2024-03-26 8:34 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-26 8:33 Sergey Bronnikov via Tarantool-patches [this message] 2024-03-26 8:33 ` [Tarantool-patches] [PATCH luajit 1/6] ci: execute LuaJIT tests with GCC 10 and ASAN Sergey Bronnikov via Tarantool-patches 2024-03-26 9:51 ` Sergey Kaplun via Tarantool-patches 2024-03-26 8:33 ` [Tarantool-patches] [PATCH luajit 2/6] test: refactor CMake macro LibRealPath Sergey Bronnikov via Tarantool-patches 2024-03-26 9:57 ` Sergey Kaplun via Tarantool-patches 2024-03-26 8:33 ` [Tarantool-patches] [PATCH luajit 3/6] test: move LibRealPath to the separate module Sergey Bronnikov via Tarantool-patches 2024-03-26 10:01 ` Sergey Kaplun via Tarantool-patches 2024-03-26 8:33 ` [Tarantool-patches] [PATCH luajit 4/6] test: more cautious usage of LD_PRELOAD for ASan Sergey Bronnikov via Tarantool-patches 2024-03-26 10:04 ` Sergey Kaplun via Tarantool-patches 2024-03-26 8:33 ` [Tarantool-patches] [PATCH luajit 5/6] test: fix lj-802-panic-at-mcode-protfail GCC+ASan Sergey Bronnikov via Tarantool-patches 2024-03-26 10:08 ` Sergey Kaplun via Tarantool-patches 2024-03-26 15:22 ` Sergey Bronnikov via Tarantool-patches 2024-03-26 8:33 ` [Tarantool-patches] [PATCH luajit 6/6] cmake: replace prove with CTest Sergey Bronnikov via Tarantool-patches 2024-03-26 11:03 ` Sergey Kaplun via Tarantool-patches 2024-04-01 14:28 ` Sergey Bronnikov via Tarantool-patches 2024-04-01 18:46 ` Sergey Kaplun via Tarantool-patches 2024-04-11 16:47 ` [Tarantool-patches] [PATCH luajit 0/6][v5] " Sergey Kaplun 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=cover.1711441864.git.sergeyb@tarantool.org \ --to=tarantool-patches@dev.tarantool.org \ --cc=estetus@gmail.com \ --cc=m.kokryashkin@tarantool.org \ --cc=skaplun@tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH luajit 0/6][v5] cmake: replace prove with CTest' \ /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