Adapt using tarantoolctl for static build packages and tarantool version 3.0+
#400
Assignees
Labels
feature
A new functionality
Comments
This was referenced Jul 24, 2023
ylobankov
pushed a commit
that referenced
this issue
Jul 28, 2023
Now test-run can run tests against Tarantool binary that can be located
anywhere.
Add an additional argument `--executable` [string] for test-run. This
parameter sets a fixed path to the executable file.
Warning: test library binaries are required to run tests anyway.
Example usage:
$ ./test-run.py --executable /foo/bar/tarantool
In scope of #400
ylobankov
pushed a commit
that referenced
this issue
Jul 28, 2023
In the near future we plan to test Tarantool installed from a DEB/RPM package. Since 3.0.0-alpha1 release [1] Tarantool packages don't have the tarantoolctl utility inside [2][3]. So tarantoolctl was added to the root directory of the project. Now test-run will always use the local tarantoolctl. [1] https://github.com/tarantool/tarantool/releases/tag/3.0.0-alpha1 [2] tarantool/tarantool#8771 [3] tarantool/tarantool#8866 Close #400
ylobankov
changed the title
tarantoolctl for static build and tarantool version 3.0+tarantoolctl for static build packages and tarantool version 3.0+
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The main problems, why do we need to change test-run:
tarantoolctldoes NOT get into new static build packages;tarantoolctlmay be replaced by tt (sometime in the future).The text was updated successfully, but these errors were encountered: