You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Having luatest as a submodule is inconvenient because:
To update luatest in some project using it via test-run, we have to update it in test-run first.
From point 1 it follows that all projects using test-run are bound to use the same version of luatest.
Let's drop the luatest submodule from test-run and require projects using test-run install luatest as a prerequisite, either as a submodule or from luarocks.
The text was updated successfully, but these errors were encountered:
The `test-run` project is rarely updated these days while `luatest` is
rapidly developing. Let's remove the `luatest` submodule from `test-run`
to ease luatest bumps in projects using `test-run`. Now, `luatest` is
supposed to be added as a submodule to all projects using `test-run`.
By default, `test-run` looks for `luatest` in `../third_party/luatest`,
but this can be overridden with the new `--luatestdir option`.
Note that we also remove the `checks` submodule, which was added as
a dependency of `luatest`. It was built in Tarantool in 2.11.0 so
there's no need in it anymore.
Closes#453
Having luatest as a submodule is inconvenient because:
Let's drop the luatest submodule from test-run and require projects using test-run install luatest as a prerequisite, either as a submodule or from luarocks.
The text was updated successfully, but these errors were encountered: