Commits
- Commit:
9419ae5fdfed0da5872611ef8581b1c4e80ca2c5
- From:
- Sergey Bronnikov <sergeyb@tarantool.org>
- Via:
- Yaroslav Lobankov <y.lobankov@tarantool.org>
- Date:
ci: add integration testing for etcd-client
Add workflow job for integration testing of the etcd-client module.
NO_DOC=ci
NO_TEST=ci
NO_CHANGELOG=ci
- Commit:
f90f53900d9a2e4273411d05d8062bdeb9be2415
- From:
- Andrey Saranchin <Andrey22102001@gmail.com>
- Via:
- Serge Petrenko <35663196+sergepetrenko@users.noreply.github.com>
- Date:
test: cover port implementations with unit tests
The commit introduces new `unit/port.cc` test that covers almost all
port implementations and almost all port methods. This test was
intended as a testing point for future port changes.
Implementations `port_sql` and `port_vdbemem` and method `dump_vdbemem`
are not tested because I don't know much about the sql subsystem. For
the same reason, I didn't tested `port_dump_msgpack_with_context`.
Method `dump_msgpack_16` is not actually supported, but it is
still used for compatibility with very old connectors. The problem is I
found a bug in `port_c_dump_msgpack_16` while writing the test, and we
don't want to fix it - probably, we will get rid of this method in
future. Method `dump_plain` is not tested because it requires functions
from `console.lua` file - it is easier to test `console.push` from Lua
then loading the Lua file in unit test.
The file has .cc extension because the test requires user_cache
susbystem, which has init and free methods available only from C++
source files.
NO_CHANGELOG=test
NO_DOC=test
- Commit:
2af8611be189918acee925a1881d1188cc999868
- From:
- Andrey Saranchin <Andrey22102001@gmail.com>
- Via:
- Serge Petrenko <35663196+sergepetrenko@users.noreply.github.com>
- Date:
test: include lua headers in extern "C" scope
Lua headers don't have C++ guards which means all Lua symbols are
mangled as C++ ones when the files included in a C++ source file,
but then the linker fails because all Lua functions are exported
with C mangling. Let's include lua headers in extern "C" scope to
allow to use "lua_test_utils.h" in unit tests written in C++.
NO_CHANGELOG=test
NO_DOC=test
- Commit:
60cbfbe454c179bf97ebf23b1494e871a4befe1d
- From:
- Andrey Saranchin <Andrey22102001@gmail.com>
- Via:
- Serge Petrenko <35663196+sergepetrenko@users.noreply.github.com>
- Date:
port_c: drop assertion in port_c_dump_lua method
The method actually supports all modes of dump to Lua, but the assertion
checks that mp_object mode is never used - the commit drops the
assertion.
This mode is tested with a tuple constraint taking raw args. Along the
way, some test cases are enabled back because the bug that caused them
to be disabled has been fixed.
NO_CHANGELOG=internal
NO_DOC=internal
- Commit:
ee08747291788868ddd5fe5f0571b48c2501b89b
- From:
- Nikolay Shirokovskiy <nshirokovskiy@tarantool.org>
- Via:
- Serge Petrenko <35663196+sergepetrenko@users.noreply.github.com>
- Date:
error: hide redundant fields of box.error.unpack()
Closes #9101
@TarantoolBot document
Title: hide redundant fields of box.error.unpack()
Do not show redundant fields of box.error.unpack(). These are `base_type`,
`custom_type` and `code` if the latter is 0.
New behaviour is available if `box_error_unpack_type_and_code` compat
option is 'new'. Default value is 'old` currently.
(The https://tarantool.io/compat/box_error_unpack_type_and_code is
to be added.)