redict/tests
antirez e21e0ba3dc Sentinel test: more correct sentinels config reset.
In the initialization test for each instance we used to unregister the
old master and register it again to clear the config.
However there is a race condition doing this: as soon as we unregister
and re-register "mymaster", another Sentinel can update the new
configuration with the old state because of gossip "hello" messages.

So the correct procedure is instead, unregister "mymaster" from all the
sentinel instances, and re-register it everywhere again.
2014-06-23 14:07:47 +02:00
..
assets test-server: only listen to 127.0.0.1 2013-06-12 22:49:32 +02:00
cluster Add correct exit value to failed tests 2014-06-18 08:10:04 -04:00
helpers Regression test for issue 417 (memory leak when replicating to DB with id >= 10) 2012-03-30 10:26:07 +02:00
integration Basic tests for the ROLE command. 2014-06-23 09:08:51 +02:00
sentinel Sentinel test: more correct sentinels config reset. 2014-06-23 14:07:47 +02:00
support Test: Tcl client initial support for automatic reconnection. 2014-06-18 15:52:14 +02:00
tmp minor fixes to the new test suite, html doc updated 2010-05-14 18:48:33 +02:00
unit Test: use higher level redis.tcl proc to read replies. 2014-06-18 16:25:53 +02:00
instances.tcl Sentienl/Redis test: enable link reconnection in instances.tcl. 2014-06-18 15:55:04 +02:00
test_helper.tcl Initial HyperLogLog tests. 2014-04-03 22:16:05 +02:00