valitydev/riak_test
14
0
Fork 0
mirror of https://github.com/valitydev/riak_test.git synced 2024-11-06 00:25:22 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Remove unnecessary sleeps in verify_object_limits

Browse Source 
Discussed this with Brian and turned out they were just left over from
some debugging he'd been doing earlier. I tried the test without them
and it works fine.
This commit is contained in:
Nick Marino 2016-03-04 15:36:15 -05:00
parent d66bf7546b
commit 1d6ab06cfb
1 changed files with 0 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
tests/verify_object_limits.erl
View File

@ -137,7 +137,6 @@ verify_readrepair_ignore_max_size(C, Node1) ->
% Add intercept to treat all vnode puts as readrepairs
Intercept = {riak_kv_vnode, [{{put, 6}, put_as_readrepair},{{coord_put,6}, coord_put_as_readrepair}]},
ok = rt_intercept:add(Node1, Intercept),
timer:sleep(100),
% Do put with value greater than max size and confirm warning
lager:info("Checking readrepair put of size ~p, expecting ok result and log warning", [?MAX_SIZE*2]),
K = <<"rrsizetest">>,
@ -163,7 +162,6 @@ verify_readrepair_ignore_max_sib(C, Node1) ->
% Add intercept to spoof writes as readrepair
Intercept = {riak_kv_vnode, [{{put, 6}, put_as_readrepair},{{coord_put,6}, coord_put_as_readrepair}]},
ok = rt_intercept:add(Node1, Intercept),
timer:sleep(100),
% Verify readrepair writes return ok and log warning
lager:info("Verifying succesful put above max_siblings with readrepair"),
?assertMatch(ok, riakc_pb_socket:put(C, O)),