- 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 3 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.
-
antirez authored
There was no sane way to detect tests that may never end because of Redis bugs or tests bugs.
-
- 24 Nov, 2014 1 commit
-
-
antirez authored
-
- 14 Nov, 2014 4 commits
-
-
antirez authored
-
Matt Stancliff authored
Basically: test to make sure we can load cmsgpack and do some sanity checks to make sure pack/unpack works properly. We also have a bonus test for circular encoding and decoding because I was curious how it worked.
-
Matt Stancliff authored
Two simple decode tests added mainly to check that the 'cjson' global gets registered and is usable.
-
Matt Stancliff authored
A few people have written custom C commands because bit manipulation isn't exposed through Lua. Let's give them Mike Pall's bitop. This adds bitop 1.0.2 (2012-05-08) from http://bitop.luajit.org/ bitop is imported as "bit" into the global namespace. New Lua commands: bit.tobit, bit.tohex, bit.bnot, bit.band, bit.bor, bit.bxor, bit.lshift, bit.rshift, bit.arshift, bit.rol, bit.ror, bit.bswap Verification of working (the asserts would abort on error, so (nil) is correct): 127.0.0.1:6379> eval "assert(bit.tobit(1) == 1); assert(bit.band(1) == 1); assert(bit.bxor(1,2) == 3); assert(bit.bor(1,2,4,8,16,32,64,128) == 255)" 0 (nil) 127.0.0.1:6379> eval 'assert(0x7fffffff == 2147483647, "broken hex literals"); assert(0xffffffff == -1 or 0xffffffff == 2^32-1, "broken hex literals"); assert(tostring(-1) == "-1", "broken tostring()"); assert(tostring(0xffffffff) == "-1" or tostring(0xffffffff) == "4294967295", "broken tostring()")' 0 (nil) Tests also integrated into the scripting tests and can be run with: ./runtest --single unit/scripting Tests are excerpted from `bittest.lua` included in the bitop distribution.
-
- 29 Oct, 2014 1 commit
-
-
antirez authored
-
- 08 Oct, 2014 2 commits
- 06 Oct, 2014 5 commits
-
-
antirez authored
-
Matt Stancliff authored
-
Matt Stancliff authored
-
Matt Stancliff authored
-
Aaron Rutkovsky authored
Closes #1513
-
- 17 Sep, 2014 2 commits