5 Commits

Author	SHA1	Message	Date
nitaicaro	8fb89a5728	Fixed Tracking test “The other connection is able to get invalidations” (#7871) ... PROBLEM: [$rd1 read] reads invalidation messages one by one, so it's never going to see the second invalidation message produced after INCR b, whether or not it exists. Adding another read will block incase no invalidation message is produced. FIX: We switch the order of "INCR a" and "INCR b" - now "INCR b" comes first. We still only read the first invalidation message produces. If an invalidation message is wrongly produces for b - then it will be produced before that of a, since "INCR b" comes before "INCR a". Co-authored-by: Nitai Caro <caronita@amazon.com>	2020-09-30 19:52:01 +03:00
antirez	dec6fd3adc	Regression test for #7249.	2020-05-14 11:27:31 +02:00
antirez	8d67211450	Tracking: test expired keys notifications.	2020-04-22 11:45:34 +02:00
antirez	58d61dd639	Tracking: NOLOOP tests.	2020-04-22 11:24:19 +02:00
antirez	8ea7a3ee68	Tracking: first set of tests for the feature.	2020-02-14 14:29:00 +01:00