OS: Ubuntu 16.04

Execution time of different units:
  0 seconds - unit/printver
  0 seconds - unit/type/incr
  0 seconds - unit/auth
  0 seconds - unit/scan
  0 seconds - unit/quit
  0 seconds - unit/protocol
  1 seconds - unit/keyspace
  2 seconds - unit/multi
  2 seconds - unit/type/hash
  6 seconds - unit/type/set
  8 seconds - unit/type/zset
  8 seconds - unit/other
  9 seconds - unit/sort
  9 seconds - unit/type/string
  0 seconds - integration/logging
  1 seconds - integration/convert-zipmap-hash-on-load
  0 seconds - unit/pubsub
  2 seconds - integration/rdb
  4 seconds - integration/aof
  0 seconds - unit/introspection
  10 seconds - unit/expire
  1 seconds - unit/slowlog
  1 seconds - unit/limits
  1 seconds - unit/bitfield
  12 seconds - unit/type/list
  3 seconds - unit/bitops
  13 seconds - integration/replication-2
  5 seconds - unit/maxmemory
  14 seconds - unit/type/list-2
  6 seconds - unit/scripting
  6 seconds - unit/introspection-2
  6 seconds - unit/memefficiency
  12 seconds - unit/geo
  14 seconds - unit/hyperloglog
  28 seconds - unit/dump
  28 seconds - integration/replication-3
  32 seconds - integration/replication-4
  42 seconds - unit/aofrw
  46 seconds - unit/obuf-limits
  88 seconds - integration/replication
  90 seconds - unit/type/list-3
  107 seconds - integration/replication-psync

!!! WARNING The following tests failed:

*** [err]: Test replication partial resync: ok psync (diskless: yes, reconnect: 1) in tests/integration/replication-psync.tcl
Expected condition '[s -1 sync_partial_ok] > 0' to be true ([s -1 sync_partial_ok] > 0)
Cleanup: may take some time... OK
Makefile:225: recipe for target 'test' failed
make[1]: *** [test] Error 1
make[1]: Leaving directory '/home/hegwin/Downloads/redis-3.2.5/src'
Makefile:6: recipe for target 'test' failed
make: *** [test] Error 2

Comment From: itamarhaber

Seems to be a duplicate of https://github.com/antirez/redis/issues/2715, https://github.com/antirez/redis/issues/1417 and https://github.com/antirez/redis/issues/3497. This appears to be a false positive in slow environments - the common workaround is to use taskset for binding the testing to a CPU

Comment From: itamarhaber

Tests have been improved since - @oranagra please consider closing this and the dups.

Comment From: oranagra

yes. this test was improved in redis 6.0, and we're not going to fix the test suite of 3.2. please open a new issue if some problem is reproduced in the latest / unstable.