- 16 Jun, 2017 1 commit
-
-
xuzhou authored
-
- 15 Jun, 2017 1 commit
-
-
antirez authored
-
- 22 Apr, 2017 3 commits
-
-
antirez authored
Related to #3786.
-
antirez authored
Apparently 1.4 is too low compared to what you get in certain setups (including mine). I raised it to 1.55 that hopefully is still enough to test that the fragmentation went down from 1.7 but without incurring in issues, however the test setup may be still fragile so certain times this may lead to false positives again, it's hard to test for these things in a determinsitic way. Related to #3786.
-
oranagra authored
-
- 15 Mar, 2017 1 commit
-
-
Oran Agra authored
-
- 22 Feb, 2017 2 commits
- 20 Dec, 2016 1 commit
-
-
antirez authored
We need to report all the points added into the set, not just the ones matching the Tcl distance algo.
-
- 05 Dec, 2016 1 commit
-
-
antirez authored
The test now uses more diverse radius sizes, especially sizes near or greater the whole earth surface are used, that are known to trigger edge cases. Moreover the PRNG seeding was probably resulting into the same sequence tested over and over again, now seeding unsing the current unix time in milliseconds. Related to #3631.
-
- 18 Nov, 2016 1 commit
-
-
antirez authored
-
- 31 Oct, 2016 1 commit
-
-
antirez authored
-
- 14 Oct, 2016 1 commit
-
-
antirez authored
-
- 24 Aug, 2016 1 commit
-
-
antirez authored
-
- 27 Jul, 2016 1 commit
-
-
antirez authored
By grepping the continuous integration errors log a number of GEORADIUS tests failures were detected. Fortunately when a GEORADIUS failure happens, the test suite logs enough information in order to reproduce the problem: the PRNG seed, coordinates and radius of the query. By reproducing the issues, three different bugs were discovered and fixed in this commit. This commit also improves the already good reporting of the fuzzer and adds the failure vectors as regression tests. The issues found: 1. We need larger squares around the poles in order to cover the area requested by the user. There were already checks in order to use a smaller step (larger squares) but the limit set (+/- 67 degrees) is not enough in certain edge cases, so 66 is used now. 2. Even near the equator, when the search area center is very near the edge of the square, the north, south, west or ovest square may not be able to fully cover the specified radius. Now a test is performed at the edge of the initial guessed search area, and larger squares are used in case the test fails. 3. Because of rounding errors between Redis and Tcl, sometimes the test signaled false positives. This is now addressed. Whenever possible the original code was improved a bit in other ways. A debugging example stanza was added in order to make the next debugging session simpler when the next bug is found.
-
- 06 Jul, 2016 1 commit
-
-
antirez authored
-
- 28 Jun, 2016 3 commits
- 15 Jun, 2016 2 commits
- 05 Jun, 2016 1 commit
-
-
Pierre Chapuis authored
-
- 31 May, 2016 1 commit
-
-
antirez authored
-
- 18 May, 2016 1 commit
-
-
antirez authored
-
- 06 May, 2016 1 commit
-
-
antirez authored
-
- 25 Apr, 2016 1 commit
-
-
Oran Agra authored
-
- 18 Apr, 2016 1 commit
-
-
Damian Janowski authored
-
- 02 Mar, 2016 4 commits
- 18 Feb, 2016 1 commit
-
-
antirez authored
-
- 08 Jan, 2016 1 commit
-
-
antirez authored
This fix, provided by Paul Kulchenko (@pkulchenko), allows the Lua scripting engine to evaluate statements with a trailing comment like the following one: EVAL "print() --comment" 0 Lua can't parse the above if the string does not end with a newline, so now a final newline is always added automatically. This does not change the SHA1 of scripts since the SHA1 is computed on the body we pass to EVAL, without the other code we add to register the function. Close #2951.
-
- 11 Dec, 2015 2 commits
- 28 Nov, 2015 1 commit
-
-
antirez authored
64 bit double math is not enough to make the test passing, and rounding to 1.2999999 instead of 1.23 is not an error in the implementation. Valgrind and sometimes other archs are not able to work with 80 bit doubles.
-
- 04 Nov, 2015 1 commit
-
-
antirez authored
This test was kindly provided by Jan-Erik Rediger (@badboy here on Github) that discovered the issue. See issue #2846.
-
- 03 Nov, 2015 1 commit
-
-
antirez authored
An user raised a question about a given behavior of PFCOUNT. Added a test to show the behavior (union) is correct when most of the items are in common.
-
- 30 Oct, 2015 2 commits