- 13 Dec, 2015 2 commits
- 10 Dec, 2015 2 commits
-
-
antirez authored
The old version was modeled with two failovers, however after the first it is possible that another slave will migrate to the new master, since for some time the new master is not backed by any slave. Probably there should be some pause after a failover, before the migration. Anyway the test is simpler in this way, and depends less on timing.
-
antirez authored
-
- 15 Oct, 2015 1 commit
-
-
antirez authored
-
- 15 Sep, 2015 1 commit
-
-
antirez authored
HINCRBY* tests later used the value "tmp" that was sometimes generated by the random key generation function. The result was ovewriting what Tcl expected to be inside Redis with another value, causing the next HSTRLEN test to fail.
-
- 14 Sep, 2015 2 commits
-
-
antirez authored
Related to #2765.
-
antirez authored
MOVE was not able to move the TTL: when a key was moved into a different database number, it became persistent like if PERSIST was used. In some incredible way (I guess almost nobody uses Redis MOVE) this bug remained unnoticed inside Redis internals for many years. Finally Andy Grunwald discovered it and opened an issue. This commit fixes the bug and adds a regression test. Close #2765.
-
- 05 Aug, 2015 4 commits
- 29 May, 2015 3 commits
- 19 May, 2015 1 commit
-
-
antirez authored
-
- 15 May, 2015 1 commit
-
-
Glenn Nethercutt authored
uphold the smove contract to return 0 when the element is not a member of the source set, even if source=dest
-
- 01 Apr, 2015 1 commit
-
-
antirez authored
This should likely fix a false positive when running with the --valgrind option.
-
- 30 Mar, 2015 1 commit
-
-
antirez authored
-
- 27 Mar, 2015 1 commit
-
-
antirez authored
-
- 22 Mar, 2015 4 commits
- 18 Mar, 2015 1 commit
-
-
antirez authored
-
- 10 Feb, 2015 2 commits
-
-
antirez authored
This test on Linux was extremely slow, since in Tcl we can't enable easily tcp-nodelay, so the busy loop used to take *a lot* with bigger writes. Fixed using pipelining.
-
antirez authored
This test on Linux was extremely slow, since in Tcl we can't enable easily tcp-nodelay, so the busy loop used to take *a lot* with bigger writes. Fixed using pipelining.
-
- 22 Jan, 2015 9 commits
-
-
antirez authored
-
antirez authored
-
antirez authored
Removes some percentage of timing related failures.
-
antirez authored
Otherwise between the two commands other nodes may contact us making the next SET-CONFIG-EPOCH call impossible.
-
antirez authored
Otherwise kill_instance + restart_instance in short succession will still find the port busy and will fail.
-
antirez authored
-
antirez authored
-
Matt Stancliff authored
-
Matt Stancliff authored
-
- 09 Jan, 2015 1 commit
-
-
antirez authored
-
- 11 Dec, 2014 1 commit
-
-
Matt Stancliff authored
People mostly use SORT against lists, but our prior behavior was pretending lists were an unordered bag requiring a forced-sort when no sort was requested. We can just use the native list ordering to ensure consistency across replicaion and scripting calls. Closes #2079 Closes #545 (again)
-
- 03 Dec, 2014 1 commit
-
-
antirez authored
-
- 28 Nov, 2014 1 commit
-
-
antirez authored
start_server now uses return value from Tcl exec to get the server pid, however this introduces errors that depend from timing: a lot of the testing code base assumed the server to be actually up and running when server_start returns. So the old code that waits to see the pid in the log file was restored.
-