summaryrefslogtreecommitdiff
path: root/tests
Commit message (Collapse)AuthorAgeFilesLines
* Test: add some AOF testing to EVALSHA replication test.antirez2013-06-251-0/+17
|
* Test: EVALSHA replication.antirez2013-06-251-0/+50
|
* Test: randomInt() behavior commented.antirez2013-06-251-0/+2
|
* Test: replication-3 test speedup in master-slave setup.antirez2013-06-251-3/+6
|
* Test: regression test for #1163.antirez2013-06-191-0/+17
|
* Fix comment typo in integration/aof.tcl.antirez2013-06-191-1/+1
|
* test-server: only listen to 127.0.0.1Marc-Antoine Perennou2013-06-122-1/+2
| | | | Signed-off-by: Marc-Antoine Perennou <Marc-Antoine@Perennou.com>
* Test: avoid a false positive in min-slaves test.antirez2013-05-311-2/+2
|
* Tests added for min-slaves feature.antirez2013-05-302-0/+46
|
* Make tests compatible with new INFO replication output.antirez2013-05-301-1/+1
|
* Test default config modified to set logfile to empty string.antirez2013-05-151-1/+1
| | | | | Required because of recent changes in the way logfile is set to standard output.
* Test: more PSYNC tests (backlog TTL).antirez2013-05-091-11/+37
|
* Test: check that replication partial sync works if we break the link.antirez2013-05-082-0/+80
| | | | | The test checks both successful syncs and unsuccessful ones by changing the backlog size.
* Test: various issues with the replication-4.tcl test fixed.antirez2013-05-081-7/+8
| | | | | The test actually worked, but vars for master and slave were inverted and sometimes used incorrectly.
* Test: fix RDB test checking file permissions.antirez2013-04-231-11/+24
| | | | | | | | | | | | When the test is executed using the root account, setting the permission to 222 does not work as expected, as root can read files with 222 permission. Now we skip the test if root is detected. This fixes issue #1034 and the duplicated #1040 issue. Thanks to Jan-Erik Rediger (@badboy on Github) for finding a way to reproduce the issue.
* Test: split conceptually unrelated comments in RDB test.antirez2013-04-221-1/+3
|
* Test: remove useless statements and comments from test default config.antirez2013-04-041-324/+1
|
* Test: Extended SET tests.antirez2013-03-281-0/+42
|
* Test: regression test for issue #1026.antirez2013-03-281-0/+10
|
* Test: verify that lazy-expire works.antirez2013-03-281-0/+18
|
* Test: test replication of MULTI/EXEC.antirez2013-03-271-0/+54
|
* Test: Restore DB back to 9 after testing MULTI/EXEC with DB 5.antirez2013-03-271-1/+4
|
* Test: new functions to capture and analyze the replication stream.antirez2013-03-271-0/+53
|
* Test: obuf-limits test false positive removed.antirez2013-03-251-1/+1
| | | | Fixes #621.
* Test: make sure broken RDB checksum is detected.antirez2013-03-131-0/+19
|
* Test: more RDB loading checks.antirez2013-03-131-0/+32
| | | | A test for issue #1001 is included.
* Test: check that Redis starts empty without an RDB file.antirez2013-03-121-0/+7
|
* Return a specific NOAUTH error if authentication is required.antirez2013-02-122-3/+3
|
* Test: avoid false positives in CLIENT SETNAME closed connection test.antirez2013-02-121-2/+6
|
* Test: No clients timeout while testing.antirez2013-02-051-1/+1
|
* Merge pull request #906 from jbergstroem/tclsh-agnosticSalvatore Sanfilippo2013-02-053-3/+8
|\ | | | | Make redis test suite tcl version agnostic, v2
| * Use `info nameofexectuable` to find current executableJohan Bergström2013-01-243-3/+6
| |
| * Enforce tcl 8.5 or newerJohan Bergström2013-01-241-0/+2
| |
* | Tests for keyspace notifications.antirez2013-01-281-1/+155
| |
* | Keyspace notifications: fixed a leak and a bug introduced in the latest commit.antirez2013-01-281-1/+1
| |
* | Keyspace events: it is now possible to select subclasses of events.antirez2013-01-281-1/+1
| | | | | | | | | | | | | | | | | | When keyspace events are enabled, the overhead is not sever but noticeable, so this commit introduces the ability to select subclasses of events in order to avoid to generate events the user is not interested in. The events can be selected using redis.conf or CONFIG SET / GET.
* | Enable keyspace events notification when testing.antirez2013-01-281-0/+3
|/
* UNSUBSCRIBE and PUNSUBSCRIBE: always provide a reply.antirez2013-01-211-1/+11
| | | | | | | | | | | | | | | | | | | | | UNSUBSCRIBE and PUNSUBSCRIBE commands are designed to mass-unsubscribe the client respectively all the channels and patters if called without arguments. However when these functions are called without arguments, but there are no channels or patters we are subscribed to, the old behavior was to don't reply at all. This behavior is broken, as every command should always reply. Also it is possible that we are no longer subscribed to a channels but we are subscribed to patters or the other way around, and the client should be notified with the correct number of subscriptions. Also it is not pretty that sometimes we did not receive a reply at all in a redis-cli session from these commands, blocking redis-cli trying to read the reply. This fixes issue #714.
* Slowlog: don't log EXEC but just the executed commands.antirez2013-01-191-0/+12
| | | | | | | | | | The Redis Slow Log always used to log the slow commands executed inside a MULTI/EXEC block. However also EXEC was logged at the end, which is perfectly useless. Now EXEC is no longer logged and a test was added to test this behavior. This fixes issue #759.
* Fixed many typos.guiquanz2013-01-191-1/+1
|
* Tests for CLIENT GETNAME/SETNAME.antirez2013-01-151-0/+33
|
* Test: added regression for issue #872.antirez2013-01-101-7/+27
|
* Test: fixed osx "leaks" support in test.antirez2012-12-031-1/+3
| | | | | | 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.
* Test: regression for issue #801.antirez2012-12-021-0/+21
|
* SDIFF is now able to select between two algorithms for speed.antirez2012-11-301-3/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | SDIFF used an algorithm that was O(N) where N is the total number of elements of all the sets involved in the operation. The algorithm worked like that: ALGORITHM 1: 1) For the first set, add all the members to an auxiliary set. 2) For all the other sets, remove all the members of the set from the auxiliary set. So it is an O(N) algorithm where N is the total number of elements in all the sets involved in the diff operation. Cristobal Viedma suggested to modify the algorithm to the following: ALGORITHM 2: 1) Iterate all the elements of the first set. 2) For every element, check if the element also exists in all the other remaining sets. 3) Add the element to the auxiliary set only if it does not exist in any of the other sets. The complexity of this algorithm on the worst case is O(N*M) where N is the size of the first set and M the total number of sets involved in the operation. However when there are elements in common, with this algorithm we stop the computation for a given element as long as we find a duplicated element into another set. I (antirez) added an additional step to algorithm 2 to make it faster, that is to sort the set to subtract from the biggest to the smallest, so that it is more likely to find a duplicate in a larger sets that are checked before the smaller ones. WHAT IS BETTER? None of course, for instance if the first set is much larger than the other sets the second algorithm does a lot more work compared to the first algorithm. Similarly if the first set is much smaller than the other sets, the original algorithm will less work. So this commit makes Redis able to guess the number of operations required by each algorithm, and select the best at runtime according to the input received. However, since the second algorithm has better constant times and can do less work if there are duplicated elements, an advantage is given to the second algorithm.
* SDIFF fuzz test added.antirez2012-11-301-0/+26
|
* Make an EXEC test more latency proof.antirez2012-11-291-2/+2
|
* EVALSHA is now case insensitive.antirez2012-11-221-0/+4
| | | | | | EVALSHA used to crash if the SHA1 was not lowercase (Issue #783). Fixed using a case insensitive dictionary type for the sha -> script map used for replication of scripts.
* Test: MULTI state is cleared after EXECABORT error.antirez2012-11-221-0/+11
|
* Test: make sure EXEC fails after previous transaction errors.antirez2012-11-221-0/+28
|
View Lorry Controller Status