[Tarantool-patches] [PATCH v2 3/3] test: replication/status -- fetch downstream lag field

[Cyrill Gorcunov]

Extend the test to observe downstream.lag value.

Part-of #5447

Signed-off-by: Cyrill Gorcunov <gorcunov at gmail.com>
---
 test/replication/status.result   | 8 ++++++++
 test/replication/status.test.lua | 6 ++++++
 2 files changed, 14 insertions(+)

diff --git a/test/replication/status.result b/test/replication/status.result
index a8c515dbb..9b5418da4 100644
--- a/test/replication/status.result
+++ b/test/replication/status.result
@@ -186,6 +186,14 @@ test_run:wait_cond(function()                    \
 ---
 - true
 ...
+-- gh-5447: Once replication vclock is reached there
+-- should be non infinity downstream lag, set it to some
+-- sane value but not short since there might be network
+-- lags on a low level.
+replica.downstream.lag ~= nil and replica.downstream.lag < 60
+---
+- true
+...
 --
 -- Replica
 --
diff --git a/test/replication/status.test.lua b/test/replication/status.test.lua
index 431463d8a..1ecf85382 100644
--- a/test/replication/status.test.lua
+++ b/test/replication/status.test.lua
@@ -73,6 +73,12 @@ test_run:wait_cond(function()                    \
             r[replica_id] == box.info.vclock[replica_id]) \
     end) or require('log').error(box.info)
 
+-- gh-5447: Once replication vclock is reached there
+-- should be non infinity downstream lag, set it to some
+-- sane value but not short since there might be network
+-- lags on a low level.
+replica.downstream.lag ~= nil and replica.downstream.lag < 60
+
 --
 -- Replica
 --
-- 
2.29.2