Attempt to prevent false positives in replication test.
Fix lua-cmsgpack 64 bit integer on 32 bit platform

This syncs lua-cmsgpack with the mattsta/lua-cmsgpack upstream.

Fixes #2161
Merge pull request #2162 from mattsta/fix/lua/cmsgpack/64-bit-integers-on-32-bit-platforms

Fix lua-cmsgpack 64 bit integer on 32 bit platform
Avoid valgrind memory leak false positive in processInlineBuffer().

zmalloc(0) cauesd to actually trigger a non-zero allocation since with
standard libc malloc we have our own zmalloc header for memory tracking,
but at the same time the returned pointer is at the end of the block and
not in the middle. This triggers a false positive when testing with
valgrind.

When the inline protocol args count is 0, we now avoid reallocating
c->argv, preventing the issue to happen.
Merge remote-tracking branch 'origin/unstable' into unstable
Document redis-cli --stat in --help output.
Fix DEBUG OBJECT lru field to report seconds.

Because of (not so) recent Redis changes, now the LRU internally
reported unit is milliseconds, not seconds, but the DEBUG OBJECT output
was still claiming seconds while providing milliseconds.
However OBJECT IDLETIME was working as expected, which is the correct
API to use.
fix benchmark memleak in loop mode
Merge pull request #2169 from razzle/unstable

fix benchmark memleak in loop mode
redis-benchmark: default num of requests is now 100000.

10000 completes in a too short time and may easily provide unreliable
figures because of tiny duration.
Cluster PUBLISH message: fix totlen count.

bulk_data field size was not removed from the count. It is not possible
to declare it simply as 'char bulk_data[]' since the structure is nested
into another structure.
Test framework: exit on timeout with report.

There was no sane way to detect tests that may never end because of
Redis bugs or tests bugs.
Test: try to cleanup still running Redis instances on exit.

It's hard to run the Redis test continuously if it leaks processes on
exceptions / errors.
Test: wait for actual startup in start_server.

start_server now uses return value from Tcl exec to get the server pid,
however this introduces errors that depend from timing: a lot of the
testing code base assumed the server to be actually up and running when
server_start returns.

So the old code that waits to see the pid in the log file was restored.