upstream/redis
1
0
Fork 0
mirror of https://github.com/redis/redis.git synced 2026-06-11 09:52:05 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions 3
redis/tests
History
Shubham S Taple 247307de96
Pass context to RM_GetUserUsername() to support auto memory management (#15042) 
Following #14890

## Problem
RM_GetUserUsername() documents that the returned RedisModuleString can
be freed via automatic memory management, but it always creates the
string with ctx=NULL so it cannot be tracked by RedisModule_AutoMemory.
Modules following the documentation may leak memory.

## Fix
Fixes `RedisModule_GetUserUsername` to accept a `RedisModuleCtx *` and create the returned `RedisModuleString` with that context, allowing RedisModule auto-memory management to track/free it as documented.
2026-04-28 16:45:31 +08:00
..
assets Optimistic locking for string objects - compare-and-set and compare-and-delete (#14435) 2025-10-21 10:32:49 +03:00
cluster Fix brittle assert_match patterns for unexpected slowlog fields (#14948) 2026-04-13 14:45:14 +08:00
helpers Fix gen_write_load error on MOVED/ASK during atomic-slot-migration tests (#15016) 2026-04-15 08:34:40 +08:00
integration t_string: rewrite SET GET propagation in place (#15114) 2026-04-28 10:05:59 +03:00
modules Pass context to RM_GetUserUsername() to support auto memory management (#15042) 2026-04-28 16:45:31 +08:00
sentinel Handle primary/replica clients in IO threads (#14335) 2026-01-21 16:19:12 +02:00
support Fix command-docs and corrupt-dump-fuzzer of OBJ_GCRA type (#15055) 2026-04-17 10:30:43 +03:00
tmp minor fixes to the new test suite, html doc updated 2010-05-14 18:48:33 +02:00
unit t_string: rewrite SET GET propagation in place (#15114) 2026-04-28 10:05:59 +03:00
vectorset Add daily CI for vectorset (#14302) 2025-12-10 08:52:43 +08:00
instances.tcl Support Tcl 9.0 in Redis test suite (#14787) 2026-02-28 14:07:25 +08:00
README.md Add thread sanitizer run to daily CI (#13964) 2025-06-02 10:13:23 +03:00
test_helper.tcl Chore complete Tcl 9 support and fix regressions in test suite (#14845) 2026-03-06 13:27:56 +08:00

README.md

Redis Test Suite

The normal execution mode of the test suite involves starting and manipulating local redis-server instances, inspecting process state, log files, etc.

The test suite also supports execution against an external server, which is enabled using the --host and --port parameters. When executing against an external server, tests tagged external:skip are skipped.

There are additional runtime options that can further adjust the test suite to match different external server configurations:

Option Impact
--singledb Only use database 0, don't assume others are supported.
--ignore-encoding Skip all checks for specific encoding.
--ignore-digest Skip key value digest validations.
--cluster-mode Run in strict Redis Cluster compatibility mode.
--large-memory Enables tests that consume more than 100mb

Tags

Tags are applied to tests to classify them according to the subsystem they test, but also to indicate compatibility with different run modes and required capabilities.

Tags can be applied in different context levels:

  • start_server context
  • tags context that bundles several tests together
  • A single test context.

The following compatibility and capability tags are currently used:

Tag Indicates
external:skip Not compatible with external servers.
cluster:skip Not compatible with --cluster-mode.
large-memory Test that requires more than 100mb
tls:skip Not compatible with --tls.
tsan:skip Not compatible with running under thread sanitizer.
needs:repl Uses replication and needs to be able to SYNC from server.
needs:debug Uses the DEBUG command or other debugging focused commands (like OBJECT REFCOUNT).
needs:pfdebug Uses the PFDEBUG command.
needs:config-maxmemory Uses CONFIG SET to manipulate memory limit, eviction policies, etc.
needs:config-resetstat Uses CONFIG RESETSTAT to reset statistics.
needs:reset Uses RESET to reset client connections.
needs:save Uses SAVE or BGSAVE to create an RDB file.

When using an external server (--host and --port), filtering using the external:skip tags is done automatically.

When using --cluster-mode, filtering using the cluster:skip tag is done automatically.

When not using --large-memory, filtering using the largemem:skip tag is done automatically.

In addition, it is possible to specify additional configuration. For example, to run tests on a server that does not permit SYNC use:

./runtest --host <host> --port <port> --tags -needs:repl