- 27 Feb, 2014 3 commits
-
-
antirez authored
-
antirez authored
-
antirez authored
It was verified in practice that this test is able to stress much more the implementation by introducing errors that were only trivially to detect with different offsets but impossible to detect starting always at zero and counting bits the full length of the string.
-
- 25 Feb, 2014 8 commits
-
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
An unit can abort in the middle for an error. The next unit should not assume that the instances are in a clean state, and must restart what was left killed.
-
antirez authored
Sentinel tests are designed to be dependent on the previous tests in the same unit, so usually we can't continue with the next test in the same unit if a previous test failed.
-
antirez authored
The test was previously performed by removing the master from the Sentinel monitored masters. The test with the Sentinels crashed is more similar to real-world partitions / failures.
-
antirez authored
Also kill_instance was modified to warn when a test will try to kill the same instance multiple times for error.
-
- 24 Feb, 2014 3 commits
-
-
antirez authored
The area a number of mandatory tests to craete a stable setup for testing that is not too sensitive to timing issues. All those tests moved to includes/init-tests, and marked as (init).
-
antirez authored
The new common initialization code used to start a new unit already set the timeout to 2000 milliseconds.
-
antirez authored
-
- 23 Feb, 2014 3 commits
- 22 Feb, 2014 1 commit
-
-
antirez authored
It is now possible to kill and restart sentinel or redis instances for more real-world testing. The 01 unit tests the capability of Sentinel to update the configuration of Sentinels rejoining the cluster, however the test is pretty trivial and more tests should be added.
-
- 20 Feb, 2014 2 commits
- 19 Feb, 2014 3 commits
- 18 Feb, 2014 6 commits
- 17 Feb, 2014 3 commits
-
-
antirez authored
Nothing tested at all so far... Just the infrastructure spawning N Sentinels and N Redis instances that the test will use again and again.
-
antirez authored
-
antirez authored
Some inline test moved into server_is_up procedure. Also find_available_port was moved into util since it is going to be used for the Sentinel test as well.
-
- 13 Feb, 2014 1 commit
-
-
antirez authored
It was verified that reverting the commit that fixes the bug, the test no longer passes.
-
- 31 Jan, 2014 1 commit
-
-
antirez authored
The Redis test uses a server-clients model in order to parallelize the execution of different tests. However in recent versions of osx not setting the channel to a binary encoding caused issues even if AFAIK no binary data is really sent via this channel. However now the channels are deliberately set to a binary encoding and this solves the issue. The exact issue was the test not terminating and giving the impression of running forever, since test clients or servers were unable to exchange the messages to continue.
-
- 09 Jan, 2014 1 commit
-
-
antirez authored
-
- 08 Jan, 2014 1 commit
-
-
antirez authored
-
- 13 Dec, 2013 1 commit
-
- 08 Dec, 2013 1 commit
-
-
Yossi Gottlieb authored
-
- 25 Nov, 2013 1 commit
-
-
antirez authored
Fixes issue #1298.
-
- 05 Nov, 2013 1 commit
-
-
antirez authored
-