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
It is not as trivial as I thought - URIs are fixed in config. Possible solution - start tarantools on zero port, collect real ports, fill them into a config, use that config.
use_unix_sockets and use_unix_sockets_iproto options did help me for graphql (if you are about flaky fails). There is also an issue in test-run to fix that: tarantool/test-run#141 (but nobody will do it, I think).
@Totktonada - not about flakiness. It is about a necessity to write all the URIs into configuration tables/files before Tarantool start. If do so, 1) parallel tests would collide on the same ports, 2) ports could be occupied already by not Tarantool. Probably unix sockets could help, if they are stored separately for each test in var/ dir. Are they? Then I could hardcode them into configs, and at the same time do not bump into collisions of different tests.
For that it is required to use zero port to bind, and deal with filtering out all the URIs from result files.
The text was updated successfully, but these errors were encountered: