From: Maxim Kokryashkin via Tarantool-patches <tarantool-patches@dev.tarantool.org> To: Sergey Bronnikov <sergeyb@tarantool.org> Cc: Maxim Kokryashkin <max.kokryashkin@gmail.com>, tarantool-patches@dev.tarantool.org Subject: Re: [Tarantool-patches] [PATCH luajit v5 2/2] test: add tests for debugging extensions Date: Tue, 19 Dec 2023 17:34:10 +0300 [thread overview] Message-ID: <w4pvajwbdlqlvu474adsqroqu6cguwln6aulrvz5zpvre3eaol@y66fnaqtxjvp> (raw) In-Reply-To: <b4c7a4fd-035b-4076-8364-eb92f34f2557@tarantool.org> Hi! Thanks for the review! Fixed your comments, except for the comment about CMake policy. The policy you've mentioned is too new to include in our CMakeLists.txt. Branch is force pushed, diff is below: === diff --git a/test/LuaJIT-debug-extensions-tests/CMakeLists.txt b/test/LuaJIT-debug-extensions-tests/CMakeLists.txt index 3b38201d..1956cf2a 100644 --- a/test/LuaJIT-debug-extensions-tests/CMakeLists.txt +++ b/test/LuaJIT-debug-extensions-tests/CMakeLists.txt @@ -6,6 +6,15 @@ add_custom_target(LuaJIT-lldb-extension-tests DEPENDS ${LUAJIT_TEST_BINARY} ) +# Skip tests for Tarantool. +if(ENABLE_BUNDLED_LUAJIT) + message(WARNING + "Tarantool build, LuaJIT-lldb-extension-tests and " + "LuaJIT-gdb-extension-tests are dummy" + ) + return() +endif() + # Debug info is required for testing of extensions. if(NOT (CMAKE_BUILD_TYPE MATCHES Debug)) message(WARNING @@ -53,7 +56,7 @@ if(GDB) "DEBUGGER_COMMAND=${GDB}" ) add_custom_command(TARGET LuaJIT-gdb-extension-tests - COMMENT "Running luajit_dbg.py tests with gdb" + COMMENT "Running debug extension tests with gdb" COMMAND ${GDB_TEST_ENV} ${PYTHON_EXECUTABLE} ${TEST_SCRIPT_PATH} WORKING_DIRECTORY ${CMAKE_CURRENT_BINARY_DIR} @@ -68,7 +71,7 @@ if(LLDB) "DEBUGGER_COMMAND=${LLDB}" ) add_custom_command(TARGET LuaJIT-lldb-extension-tests - COMMENT "Running luajit_dbg.py tests with lldb" + COMMENT "Running debug extension tests with lldb" COMMAND ${LLDB_TEST_ENV} ${PYTHON_EXECUTABLE} ${TEST_SCRIPT_PATH} WORKING_DIRECTORY ${CMAKE_CURRENT_BINARY_DIR} diff --git a/test/LuaJIT-debug-extensions-tests/debug-extension-tests.py b/test/LuaJIT-debug-extensions-tests/debug-extension-tests.py index 6ef87473..380e4324 100644 --- a/test/LuaJIT-debug-extensions-tests/debug-extension-tests.py +++ b/test/LuaJIT-debug-extensions-tests/debug-extension-tests.py @@ -247,4 +247,5 @@ for test_cls in TestCaseBase.__subclasses__(): test_cls.test = lambda self: self.check() if __name__ == '__main__': + # XXX: Verbosity level 2 is the most verbose. unittest.main(verbosity=2) === Regards, Maxim Kokryashkin
next prev parent reply other threads:[~2023-12-19 14:34 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-06 14:14 [Tarantool-patches] [PATCH luajit v5 0/2] debug: generalized extension Maxim Kokryashkin via Tarantool-patches 2023-12-06 14:14 ` [Tarantool-patches] [PATCH luajit v5 1/2] " Maxim Kokryashkin via Tarantool-patches 2023-12-19 8:01 ` Sergey Bronnikov via Tarantool-patches 2023-12-06 14:14 ` [Tarantool-patches] [PATCH luajit v5 2/2] test: add tests for debugging extensions Maxim Kokryashkin via Tarantool-patches 2023-12-19 8:16 ` Sergey Bronnikov via Tarantool-patches 2023-12-19 14:34 ` Maxim Kokryashkin via Tarantool-patches [this message] 2023-12-20 12:23 ` Sergey Bronnikov 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=w4pvajwbdlqlvu474adsqroqu6cguwln6aulrvz5zpvre3eaol@y66fnaqtxjvp \ --to=tarantool-patches@dev.tarantool.org \ --cc=m.kokryashkin@tarantool.org \ --cc=max.kokryashkin@gmail.com \ --cc=sergeyb@tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH luajit v5 2/2] test: add tests for debugging extensions' \ /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