diff options
| author | antirez <antirez@gmail.com> | 2017-04-14 17:53:11 +0200 |
|---|---|---|
| committer | antirez <antirez@gmail.com> | 2017-04-18 16:17:42 +0200 |
| commit | e47c8e3f6aedb9ca22d87b091c3fad38c768c90e (patch) | |
| tree | 2b9dfdb98d7963b6ed47708405150b6db680d722 | |
| parent | 1e659a04cf19e4349c8dbba931d1606336970b8c (diff) | |
| download | redis-e47c8e3f6aedb9ca22d87b091c3fad38c768c90e.tar.gz | |
Test: fix, hopefully, false PSYNC failure like in issue #2715.
And many other related Github issues... all reporting the same problem.
There was probably just not enough backlog in certain unlucky runs.
I'll ask people that can reporduce if they see now this as fixed as
well.
| -rw-r--r-- | tests/integration/replication-psync.tcl | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/tests/integration/replication-psync.tcl b/tests/integration/replication-psync.tcl index da1e9cf5b..2b9e13f50 100644 --- a/tests/integration/replication-psync.tcl +++ b/tests/integration/replication-psync.tcl @@ -110,7 +110,7 @@ foreach diskless {no yes} { test_psync {no reconnection, just sync} 6 1000000 3600 0 { } $diskless 0 - test_psync {ok psync} 6 1000000 3600 0 { + test_psync {ok psync} 6 100000000 3600 0 { assert {[s -1 sync_partial_ok] > 0} } $diskless 1 |