- 02 Feb, 2016 1 commit
-
-
antirez authored
-
- 01 Oct, 2015 1 commit
-
-
antirez authored
-
- 05 Aug, 2015 1 commit
-
-
antirez authored
-
- 31 Mar, 2015 1 commit
-
-
antirez authored
This should likely fix a false positive when running with the --valgrind option.
-
- 21 Jan, 2015 1 commit
-
-
Matt Stancliff authored
-
- 09 Jan, 2015 1 commit
-
-
antirez authored
-
- 02 Jan, 2015 1 commit
-
-
Matt Stancliff authored
This replaces individual ziplist vs. linkedlist representations for Redis list operations. Big thanks for all the reviews and feedback from everybody in https://github.com/antirez/redis/pull/2143
-
- 28 Nov, 2014 2 commits
-
-
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.
-
antirez authored
It's hard to run the Redis test continuously if it leaks processes on exceptions / errors.
-
- 29 Sep, 2014 2 commits
-
-
Matt Stancliff authored
-
Matt Stancliff authored
-
- 25 Aug, 2014 1 commit
-
-
Mariano Pérez Rodríguez authored
Uses ANSI "default background" color code after closing tests so any non-black terminals don't remain polluted. Fixes #1649 Closes #1912
-
- 10 Jul, 2014 1 commit
-
-
antirez authored
-
- 30 Jun, 2014 1 commit
-
-
antirez authored
The function will only return ports that have also port+10000 free, so that Redis Cluster instances can be executed at the returned port.
-
- 18 Jun, 2014 2 commits
- 23 May, 2014 1 commit
-
-
Matt Stancliff authored
Previously the PID format was: [PID] Timestamp But it recently changed to: PID:X Timestamp The tcl testing framework was grabbing the PID from \[\d+\], but that's not valid anymore. Now we grab the pid from "PID: <PID>" in the part of Redis startup output to the right of the ASCII logo.
-
- 14 May, 2014 1 commit
-
-
antirez authored
-
- 13 May, 2014 2 commits
-
-
antirez authored
Better handling of connection errors in order to update the table and recovery, populate the startup nodes table after fetching the list of nodes. More work to do about it, it is still not as reliable as redis-rb-cluster implementation which is the minimal reference implementation for Redis Cluster clients.
-
antirez authored
-
- 07 May, 2014 1 commit
-
-
antirez authored
Sometimes the process is still there but no longer in a state that can be checked (after being killed). This used to happen after a call to SHUTDOWN NOSAVE in the scripting unit, causing a false positive.
-
- 02 May, 2014 4 commits
- 30 Apr, 2014 2 commits
- 25 Mar, 2014 1 commit
-
-
antirez authored
-
- 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.
-
- 17 Feb, 2014 2 commits
- 25 Jun, 2013 1 commit
-
-
antirez authored
-
- 30 May, 2013 1 commit
-
-
antirez authored
-
- 12 Feb, 2013 1 commit
-
-
antirez authored
-
- 03 Dec, 2012 1 commit
-
-
antirez authored
Due to changes in recent releases of osx leaks utility, the osx leak detection no longer worked. Now it is fixed in a way that should be backward compatible.
-
- 24 Oct, 2012 1 commit
-
-
YAMAMOTO Takashi authored
-
- 11 Jun, 2012 1 commit
-
-
antirez authored
A new stress test was added to stress test the code converting a ziplist into an hash table. In this commit also randomValue helper function was modified to also return negative values.
-
- 02 Jun, 2012 1 commit
-
-
antirez authored
wait_for_condition is now used instead of the usual "after 1000" (that is the way to sleep in Tcl). This should avoid to find the replica in a state where it is loading the RDB in memory, returning -LOADING error. This test used to fail when running the test over valgrind, due to the added latencies.
-
- 25 May, 2012 1 commit
-
- 22 May, 2012 1 commit
-
-
antirez authored
Due to a change in the format of the bug report in case of crash of failed assertion the test suite was no longer able to properly log it. Instead just a protocol error was logged by the Redis TCL client that provided no clue about the actual problem. This commit resolves the issue by logging everything from the first line of the log including the string REDIS BUG REPORT, till the end of the file.
-