- 18 6月, 2014 2 次提交
-
-
由 antirez 提交于
Functionally the same, but makes cherry picking simpler.
-
由 Matt Stancliff 提交于
(Note from @antirez: modified to apply to 2.8)
-
- 21 3月, 2014 2 次提交
- 05 3月, 2014 5 次提交
- 25 2月, 2014 7 次提交
-
-
由 antirez 提交于
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 提交于
Also kill_instance was modified to warn when a test will try to kill the same instance multiple times for error.
-
由 antirez 提交于
-
由 antirez 提交于
Pause the test with running instances available for state inspection on error.
-
由 antirez 提交于
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.
-
由 antirez 提交于
Most units will start with these two basic tests to create an environment where the real tests are ran.
-
由 antirez 提交于
-
- 20 2月, 2014 3 次提交
- 18 2月, 2014 1 次提交
-
-
由 antirez 提交于
Nothing tested at all so far... Just the infrastructure spawning N Sentinels and N Redis instances that the test will use again and again.
-