Skip to content
Snippets Groups Projects
user avatar
Serge Petrenko authored
The test used to fail occasionally with a following error:

```
[001] box/net.box.test.lua                                            [ fail ]
[001]
[001] Test failed! Result content mismatch:
[001] —- box/net.box.result  Thu Jun 13 06:16:34 2019
[001] +++ box/net.box.reject  Fri Jun 14 04:50:55 2019
[001] @@ -3774,23 +3774,23 @@
[001]  ...
[001]  test_run:grep_log('default', 'Got a corrupted row.*')
[001]  —-
[001] — 'Got a corrupted row:'
[001] +- null
[001]  ...
[001]  test_run:grep_log('default', '00000000:.*')
[001]  —-
[001] — '00000000: A3 02 D6 5A E4 D9 E7 68 A1 53 8D 53 60 5F 20 3F '
[001] +- null
[001]  ...
[001]  test_run:grep_log('default', '00000010:.*')
[001]  —-
[001] — '00000010: D8 E2 D6 E2 A3 02 D6 5A E4 D9 E7 68 A1 53 8D 53 '
[001] +- null
[001]  ...
[001]  test_run:grep_log('default', '00000020:.*')
[001]  —-
[001] — '00000020: 60 5F 20 3F D8 E2 D6 E2 A3 02 D6 5A E4 D9 E7 68 '
[001] +- null
[001]  ...
[001]  test_run:grep_log('default', '00000030:.*')
[001]  —-
[001] — '00000030: A1 53 8D 53 60 5F 20 3F D8 E2 D6 E2 '
[001] +- null
[001]  ...
[001]  test_run:grep_log('default', '00000040:.*')
[001]  —-
```

This happened because we used `grep_log` right after `socket:write`,
which should cause the expected log messages. Change to `wait_log`.

Follow-up #4273
07a84a97
History

Tarantool

Build Status Code Coverage Telegram Slack Gitter Google Groups

https://tarantool.io/en/

Tarantool is an in-memory database and application server.

Key features of the application server:

  • 100% compatible drop-in replacement for Lua 5.1, based on LuaJIT 2.1. Simply use #!/usr/bin/tarantool instead of #!/usr/bin/lua in your script.
  • full support for Lua modules and a rich set of own modules, including cooperative multitasking, non-blocking I/O, access to external databases, etc

Key features of the database:

  • ANSI SQL, including views, joins, referential and check constraints
  • MsgPack data format and MsgPack based client-server protocol
  • two data engines: 100% in-memory with optional persistence and an own implementation of LSM-tree, to use with large data sets
  • multiple index types: HASH, TREE, RTREE, BITSET
  • asynchronous master-master replication
  • authentication and access control
  • the database is just a C extension to the application server and can be turned off

Supported platforms are Linux/x86 and FreeBSD/x86, Mac OS X.

Tarantool is ideal for data-enriched components of scalable Web architecture: queue servers, caches, stateful Web applications.

To download and install Tarantool as a binary package for your OS, please visit https://tarantool.io/en/download/.

To build Tarantool from source, see detailed instructions in the Tarantool documentation at https://tarantool.io/en/doc/2.1/dev_guide/building_from_source/.

Please report bugs at https://github.com/tarantool/tarantool/issues We also warmly welcome your feedback in the discussion mailing list, tarantool@googlegroups.com.

Thank you for your interest in Tarantool!