LWW set max CAS does not take effect with 4 v- buckets in the bucket

I was using 4 v-buckets in the bucket in order to make the test run faster and observed this issue. The functionality works correctly with 1024 v-buckets.

This is a test case which:

• sets the system clock ahead 1 hour
• does mutations so all the v-bucket CASs are poisoned
• set the system clock back 1 hour
• set max CAS for all v-buckets to a value 30 minutes behind the poisoned CAS
• do a set for a new key - the CAS reflects the poisoned CAS

The test runner test requires these two commits which are under review: http://review.couchbase.org/#/c/69039/ and http://review.couchbase.org/#/c/69037/.

The test runner command line is:

./testrunner -i ~/servers/1node.ini  -t epengine.lww_stats.LWWStatsTests.test_drift_stats,vbuckets=1024,conflict_resolution=lww

And the .ini file should look like:

[global]

username:root

password:couchbase

port:8091

[membase]

rest_username:Administrator

rest_password:password

[servers]

1:_1

[_1]

ip:server-ip-address-goes-here

services:kv,index,n1ql