[Tarantool-patches] [PATCH] luajit - avoid hardcode of paths to luajit test

Igor Munkin imun at tarantool.org
Thu Oct 15 23:41:36 MSK 2020


Timur,

Thanks for your patch! It's worth to mention the fact we are working on
self-sufficient LuaJIT testing[1], so this mess will be gone in a while.

Please, consider the comments regarding your patch are below.

At first, CI is red[2], so unfortunately, the patch doesn't work...

Please adjust the commit subject consdering our guidelines[3]. I propose
the following: s/luajit -/test:/.

On 15.10.20, Timur Safin wrote:
> We try to avoid hardcode of paths to LuaJIT tests, which
> live in the 3rd party repository and might get updated
> without our notice.

Well, your approach definitely simplifies the maintenance, *but* the
patch is not related to th original problem we faced recently.

> 
> - to simplify cmake code we introduce symlink inside of `test`
>   directory which is now pointing to `third_party/luajit/test`
>   subdirectory

I prefer the way the symlink to <small> tests is created. However, IIRC
such approach contradicts with <add_subdirectory> behaviour, since there
is not such path at the proper CMake stage. Feel free to correct me if
I'm wrong. It would be perfect, if the symlink to the test directory
can be created at the configuration step.

There is also another approach: we can add the root CMakeLists.txt in
the LuaJIT test directory to enclose all necessary activity there.
This one look much more CMake-way, doesn't it?

> - and we use `file(GLOB...)` statement now to propagate list
>   of all available test directories we found inside of luajit
>   submodule.
> 
> Closes #5425
> ---
>  test/CMakeLists.txt | 14 +++++++++++---
>  test/luajit         |  1 +
>  2 files changed, 12 insertions(+), 3 deletions(-)
>  create mode 120000 test/luajit
> 

<snipped>

> -- 
> 2.20.1
> 

[1]: https://github.com/tarantool/tarantool/issues/4862
[2]: https://gitlab.com/tarantool/tarantool/-/pipelines/203157106
[3]: https://www.tarantool.io/en/doc/latest/dev_guide/developer_guidelines/#how-to-write-a-commit-message

-- 
Best regards,
IM


More information about the Tarantool-patches mailing list