[Tarantool-patches] [PATCH v3 luajit 1/2] cmake: run tests with Valgrind

Thu Nov 14 17:04:53 MSK 2024

Hi, Maksim!
Thanks for the patch!
Please consider my comments below.

On 11.11.24, mandesero at gmail.com wrote:
> From: Maksim Tiushev <mandesero at gmail.com>
> 
> This patch enables running tests with Valgrind. Custom Valgrind testing
> options can be configured by setting the `VALGRIND_OPTIONS` variable.
> Please note that this environment variable must be set before building,
> and any updates to it will require a project rebuild. By default, the
> suppression file is set to `src/lj.supp`.

There is a `VALGRIND_OPTS` variable [1] that we can set -- it makes the
usage of valgrind more flexible -- we can define any necessary flags in
the command line (not at the building stage).

> 
> Also this patch disables the following tests when running with Valgrind

Typo: s/Also/Also,/

> due to failures:
> 
> Disabled due #10803:

Typo: s<#10803><tarantool/tarantool#10803>

>   - test/tarantool-tests/gh-7264-add-proto-trace-sysprof-default.test.lua

Nit: Commit line width is more than 72 symbols.

>   - test/tarantool-tests/lj-512-profiler-hook-finalizers.test.lua
>   - test/tarantool-tests/lj-726-profile-flush-close.test.lua
>   - test/tarantool-tests/misclib-sysprof-lapi.test.lua
> 
> Timed out due to running under Valgrind:
>   - test/tarantool-tests/gh-7745-oom-on-trace.test.lua
>   - test/tarantool-tests/lj-1034-tabov-error-frame.test.lua
> 
> Part of #3705

Typo: s<#3705><tarantool/tarantool#3705>

> ---
>  CMakeLists.txt                                   |  5 +++++
>  test/CMakeLists.txt                              | 16 ++++++++++++++++
>  test/tarantool-tests/CMakeLists.txt              |  3 ++-
>  .../gh-7745-oom-on-trace.test.lua                |  1 +
>  .../lj-1034-tabov-error-frame.test.lua           |  1 +
>  .../lj-512-profiler-hook-finalizers.test.lua     |  5 ++++-
>  .../lj-726-profile-flush-close.test.lua          |  5 ++++-
>  ...7264-add-proto-trace-sysprof-default.test.lua |  2 ++
>  .../profilers/misclib-sysprof-lapi.test.lua      |  2 ++
>  9 files changed, 37 insertions(+), 3 deletions(-)
> 
> diff --git a/CMakeLists.txt b/CMakeLists.txt
> index aa2103b3..854b3613 100644
> --- a/CMakeLists.txt
> +++ b/CMakeLists.txt

<snipped>

> diff --git a/test/CMakeLists.txt b/test/CMakeLists.txt
> index 0db2dd8b..3cc0ddbc 100644
> --- a/test/CMakeLists.txt
> +++ b/test/CMakeLists.txt
> @@ -69,6 +69,22 @@ add_custom_target(${PROJECT_NAME}-lint DEPENDS
>  )
>  
>  set(LUAJIT_TEST_COMMAND "${LUAJIT_TEST_BINARY} -e dofile[[${LUAJIT_TEST_INIT}]]")
> +
> +if(LUAJIT_USE_VALGRIND)
> +  if (NOT LUAJIT_USE_SYSMALLOC)
> +    message(WARNING
> +      "LUAJIT_USE_SYSMALLOC option is mandatory for Valgrind's memcheck tool"
> +      " on x64 and the only way to get useful results from it for all other"
> +      " architectures.")
> +  endif()
> +
> +  find_program(VALGRIND valgrind)
> +  set(LUAJIT_TEST_VALGRIND_OPTS
> +    "--suppressions=${LUAJIT_SOURCE_DIR}/lj.supp $ENV{VALGRIND_OPTIONS}")

I suppose that we can drop $ENV{VALGRIND_OPTIONS}, since there is a
`VALGRIND_OPTS` variable [1] that we can set -- it makes the usage of
valgrind more flexible -- we can define any necessary flags in the
command line (not at the building stage).

Therefore, `LUAJIT_TEST_VALGRIND_OPTS` may be renamed to
`LUAJIT_TEST_VALGRIND_SUPP`.

> +  set(LUAJIT_TEST_COMMAND
> +    "${VALGRIND} ${LUAJIT_TEST_VALGRIND_OPTS} ${LUAJIT_TEST_COMMAND}")
> +endif()
> +
>  separate_arguments(LUAJIT_TEST_COMMAND)
>  
>  set(CMAKE_MODULE_PATH "${CMAKE_CURRENT_SOURCE_DIR}/cmake")
> diff --git a/test/tarantool-tests/CMakeLists.txt b/test/tarantool-tests/CMakeLists.txt
> index 8bdb2cf3..39562f35 100644
> --- a/test/tarantool-tests/CMakeLists.txt
> +++ b/test/tarantool-tests/CMakeLists.txt
> @@ -110,7 +110,8 @@ foreach(test_path ${tests})
>      # LUA_CPATH and LD_LIBRARY_PATH variables and also
>      # dependencies list with libraries are set in scope of
>      # BuildTestLib macro.
> -    ENVIRONMENT "LUA_PATH=${LUA_PATH};${LUA_TEST_ENV_MORE}"
> +    ENVIRONMENT "LUA_PATH=${LUA_PATH};${LUA_TEST_ENV_MORE};\
> +LJ_USE_VALGRIND=${LUAJIT_USE_VALGRIND}"

It is better to set this variable to the `LUA_TEST_ENV_MORE` list.
Also, I suggest rename it to the `LUAJIT_TEST_USE_VALGRIND`.

>      LABELS ${TEST_SUITE_NAME}
>      DEPENDS tarantool-tests-deps
>    )
> diff --git a/test/tarantool-tests/gh-7745-oom-on-trace.test.lua b/test/tarantool-tests/gh-7745-oom-on-trace.test.lua
> index fe320251..b4ab8872 100644
> --- a/test/tarantool-tests/gh-7745-oom-on-trace.test.lua
> +++ b/test/tarantool-tests/gh-7745-oom-on-trace.test.lua
> @@ -6,6 +6,7 @@ local test = tap.test('OOM on trace'):skipcond({
>                                                     (jit.os == 'OSX'),
>    ['Disabled on MacOS due to #8652'] = jit.os == 'OSX',
>    ['Test requires JIT enabled'] = not jit.status(),
> +  ['Disabled with Valgrind (Timeout)'] = os.getenv("LJ_USE_VALGRIND") == 'ON',