| fdafe233 | 27-Jul-2016 |
antirez <[email protected]> |
Multiple GEORADIUS bugs fixed.
By grepping the continuous integration errors log a number of GEORADIUS tests failures were detected.
Fortunately when a GEORADIUS failure happens, the test suite log
Multiple GEORADIUS bugs fixed.
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.
show more ...
|
| 7ca69aff | 22-Jul-2016 |
antirez <[email protected]> |
Sentinel: new test unit 07 that tests master down conditions. |
| 5b5e6520 | 22-Jul-2016 |
antirez <[email protected]> |
Sentinel: check Slave INFO state more often when disconnected.
During the initial handshake with the master a slave will report to have a very high disconnection time from its master (since technica
Sentinel: check Slave INFO state more often when disconnected.
During the initial handshake with the master a slave will report to have a very high disconnection time from its master (since technically it was disconnected since forever, so the current UNIX time in seconds is reported).
However when the slave is connected again the Sentinel may re-scan the INFO output again only after 10 seconds, which is a long time. During this time Sentinels will consider this instance unable to failover, so a useless delay is introduced.
Actaully this hardly happened in the practice because when a slave's master is down, the INFO period for slaves changes to 1 second. However when a manual failover is attempted immediately after adding slaves (like in the case of the Sentinel unit test), this problem may happen.
This commit changes the INFO period to 1 second even in the case the slave's master is not down, but the slave reported to be disconnected from the master (by publishing, last time we checked, a master disconnection time field in INFO).
This change is required as a result of an unrelated change in the replication code that adds a small delay in the master-slave first synchronization.
show more ...
|
| 940be9ab | 06-Jul-2016 |
antirez <[email protected]> |
Regression test for issue #3333. |
| f5a7f4f2 | 04-Jul-2016 |
antirez <[email protected]> |
Fix test for new RDB checksum failure message. |
| 7a3a595f | 28-Jun-2016 |
antirez <[email protected]> |
Test: new randomized stress tester for #3343 alike bugs. |
| c75ca104 | 28-Jun-2016 |
antirez <[email protected]> |
Stress tester WIP. |
| 2c3fcf87 | 28-Jun-2016 |
antirez <[email protected]> |
Regression test for issue #3343 exact min crash sequence.
Note: it was verified that it can crash the test suite without the patch applied. |
| f1c237cb | 15-Jun-2016 |
antirez <[email protected]> |
Test TOUCH and new TTL / TYPE behavior about object access time. |
| 0cb86064 | 15-Jun-2016 |
antirez <[email protected]> |
Regression test for #3282. |
| b4e5e2ec | 31-May-2016 |
antirez <[email protected]> |
Now that SPOP can be called by scripts use BLPOP on 's' flag test. |
| df419281 | 31-May-2016 |
antirez <[email protected]> |
Test: run GEO tests by default.
Thanks to @oranagra for noticing it was missing. |
| f991cdc3 | 18-May-2016 |
antirez <[email protected]> |
Test for BITFIELD regression #3221. |
| 97ce72fa | 05-May-2016 |
antirez <[email protected]> |
Cluster test 12: reshard back just a few slots to speedup the test. |
| 65707fa6 | 05-May-2016 |
antirez <[email protected]> |
Quick fix to avoid false positive in replica migration test. |
| cfc08b65 | 25-Apr-2016 |
Oran Agra <[email protected]> |
various cleanups and minor fixes |
| 38cf2bd2 | 02-May-2016 |
antirez <[email protected]> |
Cluster regression test for #3043.
The test works but is very slow so far, since it involves resharding 1/5 of all the cluster slots from master 0 to the other 4 masters and back into the original m
Cluster regression test for #3043.
The test works but is very slow so far, since it involves resharding 1/5 of all the cluster slots from master 0 to the other 4 masters and back into the original master.
show more ...
|
| 1101b515 | 02-May-2016 |
antirez <[email protected]> |
Test ZINCRBY return value. |
| 258857cd | 02-Mar-2016 |
antirez <[email protected]> |
BITFIELD: overflow wrap behavior fuzz tester. |
| 35d05d6d | 02-Mar-2016 |
antirez <[email protected]> |
BITFIELD basic unit tests. |
| b4d65c95 | 02-Mar-2016 |
antirez <[email protected]> |
BITFIELD: overflow fuzzy testing. |
| d75e0fdb | 02-Mar-2016 |
antirez <[email protected]> |
Fix typo in bitops.tcl comment. |
| 123cd882 | 18-Feb-2016 |
antirez <[email protected]> |
GEOADD STORE/STOREDIST tests. |
| c476dbad | 15-Jan-2016 |
antirez <[email protected]> |
Test: Handle LOADING in restart_instance. |
| 3148b522 | 15-Jan-2016 |
antirez <[email protected]> |
Detect and show crashes on Sentinel/Cluster tests. |