- 03 Apr, 2014 1 commit
-
-
antirez authored
-
- 25 Mar, 2014 1 commit
-
-
antirez authored
-
- 18 Mar, 2014 3 commits
- 04 Mar, 2014 5 commits
-
-
antirez authored
This commit sets the failover timeout to 30 seconds instead of the 180 seconds default, and allows to reconfigure multiple slaves at the same time. This makes tests less sensible to timing, with the result that there are less false positives due to normal behaviors that require time to succeed or to be retried. However the long term solution is probably some way in order to detect when a test failed because of timing issues (for example split brain during leader election) and retry it.
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
- 03 Mar, 2014 4 commits
- 27 Feb, 2014 4 commits
-
-
antirez authored
-
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 2 commits