- 30 Jan, 2019 1 commit
-
-
antirez authored
-
- 28 Jan, 2019 7 commits
- 18 Jan, 2019 1 commit
-
-
antirez authored
-
- 17 Jan, 2019 1 commit
-
-
antirez authored
This way the behavior is very similar to the past one. This is useful in order to remember the user she probably failed to configure a password correctly.
-
- 12 Dec, 2018 1 commit
-
-
antirez authored
-
- 28 Nov, 2018 1 commit
-
-
Qu Chen authored
-
- 19 Nov, 2018 2 commits
- 12 Nov, 2018 1 commit
-
-
Oran Agra authored
-
- 17 Oct, 2018 1 commit
-
-
antirez authored
-
- 16 Oct, 2018 2 commits
-
-
zhaozhao.zz authored
-
antirez authored
See #5426.
-
- 13 Oct, 2018 1 commit
-
-
antirez authored
-
- 10 Oct, 2018 2 commits
- 09 Oct, 2018 2 commits
-
-
zhaozhao.zz authored
-
zhaozhao.zz authored
-
- 30 Sep, 2018 1 commit
-
- 11 Sep, 2018 2 commits
- 05 Sep, 2018 1 commit
-
-
antirez authored
-
- 04 Sep, 2018 1 commit
-
-
maya-rv authored
-
- 31 Aug, 2018 1 commit
-
-
antirez authored
See #5297.
-
- 26 Aug, 2018 1 commit
-
-
Chris Lamb authored
-
- 21 Aug, 2018 1 commit
-
-
Oran Agra authored
Few tests had borderline thresholds that were adjusted. The slave buffers test had two issues, preventing the slave buffer from growing: 1) the slave didn't necessarily go to sleep on time, or woke up too early, now using SIGSTOP to make sure it goes to sleep exactly when we want. 2) the master disconnected the slave on timeout
-
- 13 Aug, 2018 1 commit
-
-
zhaozhao.zz authored
-
- 02 Aug, 2018 3 commits
- 01 Aug, 2018 1 commit
-
-
zhaozhao.zz authored
-
- 31 Jul, 2018 1 commit
-
-
antirez authored
-
- 30 Jul, 2018 1 commit
-
-
Oran Agra authored
* allowing --single to be repeated * adding --only so that only a specific test inside a unit can be run * adding --skiptill useful to resume a test that crashed passed the problematic unit. useful together with --clients 1 * adding --skipfile to use a file containing list of tests names to skip * printing the names of the tests that are skiped by skipfile or denytags * adding --config to add config file options from command line
-
- 24 Jul, 2018 1 commit
-
-
Oran Agra authored
it looks like on slow machines we're getting: [err]: slave buffer are counted correctly in tests/unit/maxmemory.tcl Expected condition '$slave_buf > 2*1024*1024' to be true (16914 > 2*1024*1024) this is a result of the slave waking up too early and eating the slave buffer before the traffic and the test ends.
-
- 18 Jul, 2018 1 commit
-
-
Oran Agra authored
on slower machines, the active defrag test tended to fail. although the fragmentation ratio was below the treshold, the defragger was still in the middle of a scan cycle. this commit changes: - the defragger uses the current fragmentation state, rather than the cache one that is updated by server cron every 100ms. this actually fixes a bug of starting one excess scan cycle - the test lets the defragger use more CPU cycles, in hope that the defrag will be faster, but also give it more time before we give up.
-