This change replaces manual choosing an iproto port for TarantoolServer
by the auto resolving mechanism. In two words, test-run always provides
'127.0.0.1:0' as a value for LISTEN env variable that is used in a lua
file to start a tarantool instance. In this way, the port will be picked
automatically, and we are getting the real value of it via the admin
console by executing box.info.listen that is available for tarantool
version >= 2.4.1, and special lua script intended for tarantool version
< 2.4.1.
The same for AppServer, test-run always provides '127.0.0.1:0' as a
value for LISTEN env variable that is used in a lua test script. In
this way, the iproto port will be picked automatically, but if the test
needs the real value of the port, it has to execute box.info.listen
for tarantool version >= 2.4.1, or other lua code for tarantool version
< 2.4.1.
This change replaces manual choosing an iproto port for TarantoolServer by the auto resolving mechanism. In two words, test-run always provides '127.0.0.1:0' as a value for LISTEN env variable that is used in a lua file to start a tarantool instance. In this way, the port will be picked automatically, and we are getting the real value of it via the admin console by executing
box.info.listenthat is available for tarantool version >= 2.4.1, and special lua script intended for tarantool version < 2.4.1.The same for AppServer, test-run always provides '127.0.0.1:0' as a value for LISTEN env variable that is used in a lua test script. In this way, the iproto port will be picked automatically, but if the test needs the real value of the port, it has to execute
box.info.listenfor tarantool version >= 2.4.1, or other lua code for tarantool version < 2.4.1.Fixes #141