Tarantool development patches archive
 help / color / mirror / Atom feed
From: Sergey Bronnikov 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/6] test: introduce tests for debugging extensions
Date: Wed, 27 May 2026 12:54:30 +0300	[thread overview]
Message-ID: <2cb77f7b-40f1-4e97-8f8f-31a7dfedc167@tarantool.org> (raw)
In-Reply-To: <ahQS-SfodLS6C-Ns@root>

[-- Attachment #1: Type: text/plain, Size: 4126 bytes --]

Hi, Sergey,

LGTM with a comment below.

Sergey

On 5/25/26 12:14, Sergey Kaplun wrote:

<snipped>

>>> diff --git a/test/tarantool-debugger-tests/CMakeLists.txt b/test/tarantool-debugger-tests/CMakeLists.txt
>>> new file mode 100644
>>> index 00000000..7fd0debc
>>> --- /dev/null
>>> +++ b/test/tarantool-debugger-tests/CMakeLists.txt
>>> @@ -0,0 +1,93 @@
>>> +set(TEST_SUITE_NAME "tarantool-debugger-tests")
>>> +
>>> +# XXX: The call produces both test and target
>>> +# <tarantool-debugger-tests-deps> as a side effect.
>>> +add_test_suite_target(tarantool-debugger-tests
>>> +  LABELS ${TEST_SUITE_NAME}
>>> +  DEPENDS ${LUAJIT_TEST_BINARY}
>>> +)
>>> +
>>> +# Debug info is required for testing of extensions.
>>> +if(NOT (CMAKE_BUILD_TYPE MATCHES Debug))
>>> +  message(WARNING
>>> +    "Not a DEBUG build, tarantool-debugger-tests is dummy"
>>> +  )
>> it is not dummy, it doesn't exist at all:
>>
>> cmake -S . -B build -DCMAKE_BUILD_TYPE=Release
>>
>> cd build
>>
>> make tarantool-debugger-tests
>> make[3]: *** No rule to make target 'src/luajit', needed by
>> 'test/tarantool-debugger-tests/CMakeFiles/tarantool-debugger-tests-deps'.
>> Stop.
> Replaced elsewhere with "omitted". =================================================================== 
> diff --git a/test/tarantool-debugger-tests/CMakeLists.txt 
> b/test/tarantool-debugger-tests/CMakeLists.txt index 
> 7fd0debc..a6684e72 100644 --- 
> a/test/tarantool-debugger-tests/CMakeLists.txt +++ 
> b/test/tarantool-debugger-tests/CMakeLists.txt @@ -10,7 +10,7 @@ 
> add_test_suite_target(tarantool-debugger-tests # Debug info is 
> required for testing of extensions. if(NOT (CMAKE_BUILD_TYPE MATCHES 
> Debug)) message(WARNING - "Not a DEBUG build, tarantool-debugger-tests is dummy"
> +    "Not a DEBUG build, tarantool-debugger-tests is omitted"
>     )
>     return()
>   endif()
> @@ -22,7 +22,7 @@ endif()
>   if(CMAKE_SYSTEM_NAME STREQUAL "Darwin" AND DEFINED ENV{CI})
>     message(WARNING
>       "Interactive debugging is unavailable for macOS CI builds,"
> -    " tarantool-debugger-tests is dummy"
> +    " tarantool-debugger-tests is omitted"
>     )
>     return()
>   endif()
> @@ -31,13 +31,17 @@ if(CMAKE_VERSION VERSION_LESS "3.12")
>     #TODO:Can remove this after upgrading to CMake >= 3.12.
>     find_package(PythonInterp)
>     if(NOT PYTHONINTERP_FOUND)
> -    message(WARNING "`python` is not found, tarantool-debugger-tests is dummy")
> +    message(WARNING
> +      "`python` is not found, tarantool-debugger-tests is omitted"
> +    )
>       return()
>     endif()
>   else()
>     find_package(Python COMPONENTS Interpreter)
>     if(NOT PYTHON_FOUND)
> -    message(WARNING "`python` is not found, tarantool-debugger-tests is dummy")
> +    message(WARNING
> +      "`python` is not found, tarantool-debugger-tests is omitted"
> +    )
>       return()
>     endif()
>     set(PYTHON_EXECUTABLE "${Python_EXECUTABLE}")
> ===================================================================

Let's create a target after checking requirements:

diff --git a/test/tarantool-debugger-tests/CMakeLists.txt 
b/test/tarantool-debugger-tests/CMakeLists.txt
index 39414db3..ab90b803 100644
--- a/test/tarantool-debugger-tests/CMakeLists.txt
+++ b/test/tarantool-debugger-tests/CMakeLists.txt
@@ -1,12 +1,5 @@
  set(TEST_SUITE_NAME "tarantool-debugger-tests")

-# XXX: The call produces both test and target
-# <tarantool-debugger-tests-deps> as a side effect.
-add_test_suite_target(tarantool-debugger-tests
-  LABELS ${TEST_SUITE_NAME}
-  DEPENDS ${LUAJIT_TEST_BINARY}
-)
-
  # Debug info is required for testing of extensions.
  if(NOT (CMAKE_BUILD_TYPE MATCHES Debug))
    message(WARNING
@@ -47,6 +40,13 @@ else()
    set(PYTHON_EXECUTABLE "${Python_EXECUTABLE}")
  endif()

+# XXX: The call produces both test and target
+# <tarantool-debugger-tests-deps> as a side effect.
+add_test_suite_target(tarantool-debugger-tests
+  LABELS ${TEST_SUITE_NAME}
+  DEPENDS ${LUAJIT_TEST_BINARY}
+)
+
  set(DEBUGGER_TEST_ENV
    "LUAJIT_TEST_BINARY=${LUAJIT_TEST_BINARY}"
    # Suppresses __pycache__ generation.

<snipped>

[-- Attachment #2: Type: text/html, Size: 5772 bytes --]

  reply	other threads:[~2026-05-27  9:54 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-19 12:39 [Tarantool-patches] [PATCH v2 luajit 0/6] Unified extension for debuggers Sergey Kaplun via Tarantool-patches
2026-05-19 12:39 ` [Tarantool-patches] [PATCH v2 luajit 1/6] test: introduce tests for debugging extensions Sergey Kaplun via Tarantool-patches
2026-05-20 13:38   ` Sergey Bronnikov via Tarantool-patches
2026-05-25  9:14     ` Sergey Kaplun via Tarantool-patches
2026-05-27  9:54       ` Sergey Bronnikov via Tarantool-patches [this message]
2026-05-27 10:52         ` Sergey Kaplun via Tarantool-patches
2026-05-26 13:50   ` Evgeniy Temirgaleev via Tarantool-patches
2026-05-26 14:41     ` Sergey Kaplun via Tarantool-patches
2026-05-26 18:52       ` Evgeniy Temirgaleev via Tarantool-patches
2026-05-27  7:56         ` Sergey Kaplun via Tarantool-patches
2026-05-27 12:41   ` Sergey Bronnikov via Tarantool-patches
2026-05-19 12:39 ` [Tarantool-patches] [PATCH v2 luajit 2/6] lldb: refactor extension Sergey Kaplun via Tarantool-patches
2026-05-27 12:27   ` Sergey Bronnikov via Tarantool-patches
2026-05-19 12:39 ` [Tarantool-patches] [PATCH v2 luajit 3/6] dbg: sort initialization of commands Sergey Kaplun via Tarantool-patches
2026-05-20 13:43   ` Sergey Bronnikov via Tarantool-patches
2026-05-19 12:39 ` [Tarantool-patches] [PATCH v2 luajit 4/6] lldb: support full-range 64-bit lightuserdata Sergey Kaplun via Tarantool-patches
2026-05-27 12:28   ` Sergey Bronnikov via Tarantool-patches
2026-05-19 12:39 ` [Tarantool-patches] [PATCH v2 luajit 5/6] dbg: generalize extension Sergey Kaplun via Tarantool-patches
2026-05-27 12:38   ` Sergey Bronnikov via Tarantool-patches
2026-05-27 12:55     ` Sergey Kaplun via Tarantool-patches
2026-05-19 12:39 ` [Tarantool-patches] [PATCH v2 luajit 6/6] ci: introduce workflow to test debugger extension Sergey Kaplun via Tarantool-patches
2026-05-20 13:52   ` Sergey Bronnikov via Tarantool-patches
2026-05-25  7:00     ` Sergey Kaplun via Tarantool-patches
2026-05-27 10:57       ` Sergey Bronnikov via Tarantool-patches
2026-05-27 11:58         ` 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=2cb77f7b-40f1-4e97-8f8f-31a7dfedc167@tarantool.org \
    --to=tarantool-patches@dev.tarantool.org \
    --cc=sergeyb@tarantool.org \
    --cc=skaplun@tarantool.org \
    --subject='Re: [Tarantool-patches] [PATCH v2 luajit 1/6] test: introduce 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