tarantool / tarantool / 26272

83%

master: 88%

push

travis-ci

<a href="https://github.com/tarantool/tarantool/commit/<a class=hub.com/tarantool/tarantool/commit/192c77176cf283e9b6571061692a6259527e707c">192c77176<a href="https://github.com/tarantool/tarantool/commit/192c77176cf283e9b6571061692a6259527e707c">&quot;&gt;test: fix replication/skip_conflict_row output

Found that test replication/skip_conflict_row.test.lua fails with
output message in results file:

  [260] @@ -117,11 +117,23 @@
  [260]  -- lsn is not promoted
  [260]  lsn1 == box.info.vclock[1]
  [260]  ---
  [260] -- true
  [260] +- false
  [260]  ...
  [260]  test_run:wait_upstream(1, {status = &amp;#39;stopped&amp;#39;, message_re = &amp;quot;Duplicate key exists in unique index &amp;#39;primary&amp;#39; in space &amp;#39;test&amp;#39;&amp;quot;})
  [260]  ---
  [260] -- true
  [260] +- false
  [260] +- id: 1
  [260] +  uuid: bdbf6673-6ee4-47eb-a88d-81164f4e61c9

Test could not be restarted with checksum because of changing values
like UUID on each fail. It happend because test-run uses internal
chain of functions wait_upstream() -&amp;gt; gen_box_info_replication_cond()
which returns instance information on its fails. To avoid of it this
output was redirected to log file instead of results file.

(cherry picked from commit </a><a class="double-link" href="https://github.com/tarantool/tarantool/commit/<a class="double-link" href="https://github.com/tarantool/tarantool/commit/7398d495a8a162f928a6a3a8f0213270ef7ba853">7398d495a</a>">7398d495a</a><a href="https://github.com/tarantool/tarantool/commit/192c77176cf283e9b6571061692a6259527e707c">)

42780 of 51640 relevant lines covered (82.84%)

958018.57 hits per line