Closed Serpentian closed 1 year ago
The test fails sometimes with the following output:
Moreover, it hangs sometimes. It's probably related to vclock synchronization between replicas
The test fails sometimes with the following output:
Test-run output
```sh [001] storage-luatest/storage_2_test.lua [001] wait vclock: --- {0: 2, 1: 79} [001] ... [001] to --- {1: 80} [001] ... [001] [001] wait vclock: --- {0: 14, 1: 109, 2: 1} [001] ... [001] to --- {1: 110, 2: 1} [001] ... [001] [001] wait vclock: --- {0: 12, 1: 106} [001] ... [001] to --- {1: 107} [001] ... [001] [001] TAP version 13 [001] 1..14 [001] # Started on Mon Oct 10 15:05:25 2022 [001] # Starting group: storage. [001] ok 1 storage..test_bucket_space_trigger_sent [001] ok 2 storage..test_bucket_space_trigger_garbage [001] ok 3 storage..test_bucket_space_trigger_active [001] ok 4 storage..test_bucket_space_trigger_pinned [001] ok 5 storage..test_bucket_space_triggers_receiving [001] ok 6 storage..test_storage_callro_refro_loss [001] ok 7 storage..test_storage_callro_refrw_loss [001] # Starting group: storage.memtx_use_mvcc_engine:true [001] ok 8 storage.memtx_use_mvcc_engine:true.test_bucket_space_trigger_sent [001] ok 9 storage.memtx_use_mvcc_engine:true.test_bucket_space_trigger_garbage [001] ok 10 storage.memtx_use_mvcc_engine:true.test_bucket_space_trigger_active [001] ok 11 storage.memtx_use_mvcc_engine:true.test_bucket_space_trigger_pinned [001] ok 12 storage.memtx_use_mvcc_engine:true.test_bucket_space_triggers_receiving [001] ok 13 storage.memtx_use_mvcc_engine:true.test_storage_callro_refro_loss [001] not ok 14 storage.memtx_use_mvcc_engine:true.test_storage_callro_refrw_loss [001] # ...ming/Work/vshard/test/storage-luatest/storage_2_test.lua:86: expected: nil, actual: cdata