ok: EVAL - cmsgpack can pack double? ok: EVAL - cmsgpack can pack negative int64? ok: EVAL - cmsgpack can pack and unpack circular references? ok: EVAL - Numerical sanity check from bitop ok: EVAL - Verify minimal bitop functionality ok: EVAL - Able to parse trailing comments ok: SCRIPTING FLUSH - is able to clear the scripts cache? ok: SCRIPT EXISTS - can detect already defined scripts? ok: SCRIPT LOAD - is able to register scripts in the scripting cache ok: In the context of Lua the output of random commands gets ordered ok: AOF rewrite of list with ziplist encoding, int data ok: SORT is normally not alpha re-ordered for the scripting engine ok: SORT BY output gets ordered for scripting ok: SORT BY with GET gets ordered for scripting ok: redis.sha1hex() implementation ok: Globals protection reading an undeclared global variable ok: Globals protection setting an undeclared global* ok: Test an example script DECR_IF_GT ok: Scripting engine resets PRNG at every script execution ok: Scripting engine PRNG can be seeded correctly ok: ZREMRANGEBYLEX fuzzy test, 100 ranges in 128 element sorted set - ziplist ok: ZSETs skiplist implementation backlink consistency test - ziplist ok: AOF rewrite of list with linkedlist encoding, int data ok: AOF rewrite of set with intset encoding, string data [err]: Server is able to generate a stack trace on selected systems in tests/integration/logging.tcl expected stack trace not found into log file

Testing unit/maxmemory ok: Without maxmemory small integers are shared ok: With maxmemory and non-LRU policy integers are still shared ok: With maxmemory and LRU policy integers are not shared ok: AOF rewrite of set with hashtable encoding, string data ok: AOF rewrite of set with intset encoding, int data ok: Test replication partial resync: ok after delay (diskless: no, reconnect: 1) ok: EVAL does not leak in the Lua stack ok: EVAL processes writes from AOF in read-only slaves ok: We can call scripts rewriting client->argv from Lua ok: Call Redis command with many args from Lua (issue #1764) ok: Number conversion precision test (issue #1118) ok: String containing number precision test (regression of issue #1118) ok: Verify negative arg count is error instead of crash (issue #1842) ok: Correct handling of reused argv (issue #1939) ok: maxmemory - is the memory limit honoured? (policy allkeys-random) ok: AOF rewrite of set with hashtable encoding, int data ok: LTRIM stress testing - ziplist ok: Timedout read-only scripts can be killed by SCRIPT KILL

Testing unit/introspection ok: Slave should be able to synchronize with the master ok: CLIENT LIST ok: MONITOR can log executed commands ok: MONITOR can log commands issued by the scripting engine ok: CLIENT GETNAME should return NIL if name is not assigned ok: CLIENT LIST shows empty fields for unassigned names ok: CLIENT SETNAME does not accept spaces ok: CLIENT SETNAME can assign a name to this connection ok: CLIENT SETNAME can change the name of an existing connection ok: After CLIENT SETNAME, connection can still be closed ok: AOF rewrite of hash with ziplist encoding, string data ok: Detect write load to master

Testing unit/limits ok: ZSETs ZRANK augmented skip list stress testing - ziplist ok: ZSCORE - skiplist ok: Big Linked list: SORT BY hash field ok: ZSCORE after a DEBUG RELOAD - skiplist ok: Intset: SORT BY key ok: Intset: SORT BY key with limit ok: Intset: SORT BY hash field ok: ZSET sorting stresser - skiplist ok: Check if maxclients works refusing connections ok: Timedout script link is still usable after Lua returns

Testing unit/obuf-limits ok: Timedout scripts that modified data can't be killed by SCRIPT KILL ok: SHUTDOWN NOSAVE can kill a timedout script anyway ok: AOF rewrite of hash with hashtable encoding, string data ok: PIPELINING stresser (also a regression for the old epoll bug) ok: APPEND basics ok: APPEND basics, integer encoded values ok: MASTER and SLAVE consistency with expire ok: AOF rewrite of hash with ziplist encoding, int data ok: maxmemory - is the memory limit honoured? (policy allkeys-lru) ok: Before the slave connects we issue two EVAL commands ok: Connect a slave to the main instance ok: Now use EVALSHA against the master, with both SHAs ok: If EVALSHA was replicated as EVAL, 'x' should be '4' ok: Replication of script multiple pushes to list with BLPOP ok: EVALSHA replication when first call is readonly ok: Lua scripts using SELECT are replicated correctly ok: Hash table: SORT BY key ok: Hash table: SORT BY key with limit ok: Hash table: SORT BY hash field ok: SET 10000 numeric keys and access all them in reverse order ok: DBSIZE should be 10101 now ok: INCR against non existing key ok: INCR against key created by incr itself ok: INCR against key originally set with SET ok: INCR over 32bit value ok: INCRBY over 32bit value with over 32bit increment ok: INCR fails against key with spaces (left) ok: INCR fails against key with spaces (right) ok: INCR fails against key with spaces (both) ok: INCR fails against a key holding a list ok: DECRBY over 32bit value with over 32bit increment, negative res ok: INCR uses shared objects in the 0-9999 range

Testing unit/bitops ok: INCR can modify objects in-place ok: INCRBYFLOAT against non existing key ok: INCRBYFLOAT against key originally set with SET ok: INCRBYFLOAT over 32bit value ok: INCRBYFLOAT over 32bit value with over 32bit increment ok: INCRBYFLOAT fails against key with spaces (left) ok: INCRBYFLOAT fails against key with spaces (right) ok: INCRBYFLOAT fails against key with spaces (both) ok: INCRBYFLOAT fails against a key holding a list ok: INCRBYFLOAT does not allow NaN or Infinity ok: INCRBYFLOAT decrement ok: SETNX target key missing ok: SETNX target key exists ok: SETNX against not-expired volatile key ok: Stress test the hash ziplist -> hashtable encoding conversion ok: AOF rewrite of hash with hashtable encoding, int data ok: First server should have role slave after SLAVEOF ok: BITCOUNT returns 0 against non existing key ok: BITCOUNT against test vector #1 ok: BITCOUNT against test vector #2 ok: BITCOUNT against test vector #3 ok: BITCOUNT against test vector #4 ok: BITCOUNT against test vector #5

Testing unit/memefficiency ok: APPEND fuzzing ok: AOF rewrite of zset with ziplist encoding, string data

ok: Perform a final SAVE to leave a clean DB on disk ok: maxmemory - is the memory limit honoured? (policy volatile-lru)

Testing unit/hyperloglog ok: AOF rewrite of zset with skiplist encoding, string data ok: AOF rewrite of zset with ziplist encoding, int data ok: BITCOUNT fuzzing without start/end ok: Test replication partial resync: backlog expired (diskless: no, reconnect: 1) ok: AOF rewrite of zset with skiplist encoding, int data ok: SDIFF fuzzing ok: SINTER against non-set should throw error ok: SUNION against non-set should throw error ok: SINTER should handle non existing key as empty ok: SINTER with same integer elements but different encoding ok: SINTERSTORE against non existing keys should delete dstkey ok: SUNIONSTORE against non existing keys should delete dstkey ok: SPOP basics - hashtable ok: BGREWRITEAOF is delayed if BGSAVE is in progress ok: BGREWRITEAOF is refused if already in progress ok: SRANDMEMBER - hashtable ok: SPOP basics - intset ok: SRANDMEMBER - intset ok: SRANDMEMBER with against non existing key

ok: SRANDMEMBER with - hashtable ok: maxmemory - is the memory limit honoured? (policy volatile-random) ok: SRANDMEMBER with - intset ok: SMOVE basics - from regular set to intset ok: SMOVE basics - from intset to regular set ok: SMOVE non existing key ok: SMOVE non existing src set ok: SMOVE from regular set to non existing destination set ok: SMOVE from intset to non existing destination set ok: SMOVE wrong src key type ok: SMOVE wrong dst key type ok: SMOVE with identical source and destination ok: Connect multiple slaves at the same time (issue #141), diskless=no ok: Memory efficiency with values in range 32 ok: BITCOUNT fuzzing with start/end ok: BITCOUNT with start, end ok: BITCOUNT syntax error #1 ok: BITCOUNT regression test for github issue #582 ok: BITCOUNT misaligned prefix ok: BITCOUNT misaligned prefix + full words + remainder ok: BITOP NOT (empty string) ok: BITOP NOT (known string) ok: BITOP where dest and target are the same key ok: BITOP AND|OR|XOR don't change the string with single input key ok: BITOP missing key is considered a stream of zero ok: BITOP shorter keys are zero-padded to the key with max length ok: SETNX against expired volatile key ok: Slave should be able to synchronize with the master ok: Detect write load to master ok: DEL against expired key

ok: Zero length value in key. SET/GET/EXISTS ok: Commands pipelining ok: Non existing command ok: RENAME basic usage ok: RENAME source key should no longer exist ok: RENAME against already existing key ok: RENAMENX basic usage ok: RENAMENX against already existing key ok: RENAMENX against already existing key (2) ok: RENAME against non existing source key ok: RENAME where source and dest key is the same ok: RENAME with volatile key, should move the TTL as well ok: RENAME with volatile key, should not inherit TTL of target key ok: Test replication partial resync: no reconnection, just sync (diskless: yes, reconnect: 0) ok: maxmemory - is the memory limit honoured? (policy volatile-ttl) ok: Slave should be able to synchronize with the master ok: Detect write load to master ok: Memory efficiency with values in range 64 ok: maxmemory - only allkeys-* should remove non-volatile keys (allkeys-random) ok: BITOP and fuzzing ok: ZRANGEBYSCORE fuzzy test, 100 ranges in 100 element sorted set - skiplist ok: Test replication partial resync: ok psync (diskless: yes, reconnect: 1) ok: maxmemory - only allkeys-* should remove non-volatile keys (allkeys-lru) ok: ZRANGEBYLEX fuzzy test, 100 ranges in 100 element sorted set - skiplist ok: Memory efficiency with values in range 128 ok: intsets implementation stress testing

ok: Slave should be able to synchronize with the master ok: Detect write load to master ok: ZREMRANGEBYLEX fuzzy test, 100 ranges in 100 element sorted set - skiplist ok: ZSETs skiplist implementation backlink consistency test - skiplist ok: maxmemory - only allkeys-* should remove non-volatile keys (volatile-lru) ok: BITOP or fuzzing ok: Memory efficiency with values in range 1024 ok: maxmemory - only allkeys-* should remove non-volatile keys (volatile-random) ok: ZSETs ZRANK augmented skip list stress testing - skiplist

ok: HyperLogLog self test passes ok: PFADD without arguments creates an HLL value ok: Approximated cardinality after creation is zero ok: PFADD returns 1 when at least 1 reg was modified ok: PFADD returns 0 when no reg was modified ok: PFADD works with empty string (regression) ok: PFCOUNT returns approximated cardinality of set ok: Big Hash table: SORT BY key ok: Big Hash table: SORT BY key with limit ok: Test replication partial resync: no backlog (diskless: yes, reconnect: 1) ok: MASTER and SLAVE dataset should be identical after complex ops

ok: maxmemory - only allkeys-* should remove non-volatile keys (volatile-ttl) ok: Slave should be able to synchronize with the master ok: Detect write load to master ok: BITOP xor fuzzing ok: BITOP NOT fuzzing ok: BITOP with integer encoded source objects ok: BITOP with non string source key ok: BITOP with empty string after non empty string (issue #529) ok: BITPOS bit=0 with empty key returns 0 ok: BITPOS bit=1 with empty key returns -1 ok: BITPOS bit=0 with string less than 1 word works ok: BITPOS bit=1 with string less than 1 word works ok: BITPOS bit=0 starting at unaligned address ok: BITPOS bit=1 starting at unaligned address ok: BITPOS bit=0 unaligned+full word+reminder ok: BITPOS bit=1 unaligned+full word+reminder ok: BITPOS bit=1 returns -1 if string is all 0 bits ok: BITPOS bit=0 works with intervals ok: BITPOS bit=1 works with intervals ok: BITPOS bit=0 changes behavior if end is given ok: BITPOS bit=1 fuzzy testing using SETBIT ok: maxmemory - policy volatile-lru should only remove volatile keys. ok: HyperLogLogs are promote from sparse to dense ok: BITPOS bit=0 fuzzy testing using SETBIT

ok: Big Hash table: SORT BY hash field ok: SORT GET # ok: SORT GET ok: SORT GET (key and hash) with sanity check ok: SORT BY key STORE ok: SORT BY hash field STORE ok: SORT extracts STORE correctly ok: SORT extracts multiple STORE correctly ok: SORT DESC ok: SORT ALPHA against integer encoded strings ok: SORT sorted set ok: SORT sorted set BY nosort should retain ordering ok: SORT sorted set BY nosort + LIMIT ok: SORT sorted set BY nosort works as expected from scripts ok: SORT sorted set: +inf and -inf handling ok: SORT regression for issue #19, sorting floats ok: SORT with STORE returns zero if result is empty (github issue 224) ok: SORT with STORE does not create empty lists (github issue 224) ok: SORT with STORE removes key if result is empty (github issue 227) ok: SORT with BY and STORE should still order output ok: SORT will complain with numerical sorting and bad doubles (1) ok: SORT will complain with numerical sorting and bad doubles (2) ok: SORT BY sub-sorts lexicographically if score is the same ok: SORT GET with pattern ending with just -> does not get hash field ok: DEL all keys again (DB 0) ok: DEL all keys again (DB 1) ok: MOVE basic usage ok: MOVE against key existing in the target DB ok: MOVE against non-integer DB (#1428) ok: SORT by nosort retains native order for lists ok: SORT by nosort plus store retains native order for lists ok: SORT by nosort with limit returns based on original list order ok: MOVE can move key expire metadata as well ok: MOVE does not create an expire if it does not exist ok: SET/GET keys in different DBs

ok: MGET against non existing key ok: MGET against non-string key

ok: RANDOMKEY against empty DB ok: RANDOMKEY regression 1

ok: MSET base case ok: MSET wrong number of args ok: MSETNX with already existent key ok: MSETNX with not existing keys ok: STRLEN against non-existing key ok: STRLEN against integer-encoded value ok: STRLEN against plain string ok: SETBIT against non-existing key ok: SETBIT against string-encoded key ok: SETBIT against integer-encoded key ok: SETBIT against key with wrong type ok: SETBIT with out of range bit offset ok: SETBIT with non-bit argument ok: SORT speed, 100 element list BY key, 100 times ok: SORT speed, 100 element list BY hash field, 100 times ok: SORT speed, 100 element list directly, 100 times ok: SORT speed, 100 element list BY , 100 times ok: maxmemory - policy volatile-random should only remove volatile keys.

ok: maxmemory - policy volatile-ttl should only remove volatile keys. ok: Test replication partial resync: ok after delay (diskless: yes, reconnect: 1)

ok: SETBIT fuzzing ok: GETBIT against non-existing key ok: GETBIT against string-encoded key ok: GETBIT against integer-encoded key ok: SETRANGE against non-existing key ok: SETRANGE against string-encoded key ok: SETRANGE against integer-encoded key ok: SETRANGE against key with wrong type ok: SETRANGE with out of range offset ok: GETRANGE against non-existing key ok: GETRANGE against string value ok: GETRANGE against integer-encoded value ok: ziplist implementation: encoding stress testing ok: HyperLogLog sparse encoding stress test ok: Corrupted sparse HyperLogLogs are detected: Additionl at tail ok: Corrupted sparse HyperLogLogs are detected: Broken magic ok: Corrupted sparse HyperLogLogs are detected: Invalid encoding ok: Corrupted dense HyperLogLogs are detected: Wrong length ok: PFADD, PFCOUNT, PFMERGE type checking works ok: PFMERGE results on the cardinality of union of sets

ok: Slave should be able to synchronize with the master ok: Detect write load to master ok: Memory efficiency with values in range 16384

ok: GETRANGE fuzzing ok: Extended SET can detect syntax errors ok: Extended SET NX option ok: Extended SET XX option ok: Extended SET EX option ok: Extended SET PX option ok: Extended SET using multiple options at once ok: KEYS * two times with long key, Github issue #1208 ok: GETRANGE with huge ranges, Github issue #1844

ok: Connect multiple slaves at the same time (issue #141), diskless=yes

ok: Test replication partial resync: backlog expired (diskless: yes, reconnect: 1)

ok: Client output buffer hard limit is enforced ok: PFCOUNT multiple-keys merge returns cardinality of union ok: PFDEBUG GETREG returns the HyperLogLog raw registers ok: PFADD / PFCOUNT cache invalidation works

ok: MASTER and SLAVE consistency with EVALSHA replication

ok: Replication: commands with many arguments (issue #1221)

ok: Client output buffer soft limit is not enforced if time is not overreached ok: Client output buffer soft limit is enforced if time is overreached

               The End

Execution time of different units: 1 seconds - unit/printver 2 seconds - unit/auth 1 seconds - unit/quit 3 seconds - unit/multi 3 seconds - unit/scan 7 seconds - unit/protocol 11 seconds - unit/expire 25 seconds - unit/type/list 10 seconds - integration/aof 3 seconds - integration/rdb 3 seconds - integration/convert-zipmap-hash-on-load 45 seconds - unit/dump 1 seconds - unit/pubsub 2 seconds - unit/slowlog 11 seconds - integration/logging 57 seconds - unit/type/list-2 1 seconds - unit/introspection 2 seconds - unit/limits 15 seconds - unit/scripting 64 seconds - unit/type/hash 67 seconds - unit/other 69 seconds - unit/aofrw 93 seconds - unit/type/set 104 seconds - unit/type/zset 105 seconds - integration/replication-2 52 seconds - unit/bitops 118 seconds - unit/sort 69 seconds - unit/maxmemory 124 seconds - unit/type/list-3 67 seconds - unit/memefficiency 133 seconds - unit/basic 135 seconds - integration/replication 129 seconds - integration/replication-psync 89 seconds - unit/hyperloglog 155 seconds - integration/replication-3 153 seconds - integration/replication-4 108 seconds - unit/obuf-limits

!!! WARNING The following tests failed:

* [err]: Server is able to generate a stack trace on selected systems in tests/integration/logging.tcl expected stack trace not found into log file Cleanup: may take some time... OK make: * [test] 错误 1

Comment From: xuepd

How to solve it?

Comment From: oranagra

i'm not sure what was the problem, but we're not gonna solve any problems in reids 3.0 now anyway (certainly not one that's non-critical). i would guess that the problem was resolved by redis 5.0. redis 6.0 doesn't support CentOS6 anyway, but redis 6.2 will and all tests are passing, see https://github.com/redis/redis/pull/7707

Comment From: xhuacmer

I also meet this problem by redis 5.0. Could anyone konw how to resolve it? Is this the test case problem or code bug? I didn't find any infomation in the github.

Comment From: oranagra

this (Server is able to generate a stack trace on selected systems) is most likely a problem in the test, and even if it isn't and there's a real problem in the code, it's not a critical one (it's just a mechanism used to report crashes).

anyway i'm quite sure this problem was resolved in redis 6.0 @xhuacmer are you also using CentOS 6.x? can you can probably try redis 6.2 RC1 (6.0 won't run on that system)

Comment From: xhuacmer

@oranagra Thanks very much for reply! I am using CentOS 7.6 to build redis 5.0. Of course, I will try redis 6.2 to verify whether it's the code bug or OS environment problem. I hope it's not a code bug in redis 5.0.

Comment From: oranagra

for CentOS 7.x you can also use Redis 6.0 with some tricks:

Comment From: xhuacmer

OK, Thanks for your information! Let me try it.