[kudu-CR] fuzz-itest: fix a test failure with scan-at-snapshot

["Todd Lipcon (Code Review)" <ge...@cloudera.org>]

Todd Lipcon has posted comments on this change.

Change subject: fuzz-itest: fix a test failure with scan-at-snapshot
......................................................................


Patch Set 1:

(1 comment)

http://gerrit.cloudera.org:8080/#/c/6494/1/src/kudu/integration-tests/fuzz-itest.cc
File src/kudu/integration-tests/fuzz-itest.cc:

PS1, Line 632: saved_values_[current_time] = cur_val;
> you ran big fuzzes with this change, right? just want to make sure that the
well, isn't it limited to the total number of FLUSH_OPS entries in the test sequence? And each entry is just an int/int pair... so even a fuzz sequence of a million entries would be <100MB of memory.


-- 
To view, visit http://gerrit.cloudera.org:8080/6494
To unsubscribe, visit http://gerrit.cloudera.org:8080/settings

Gerrit-MessageType: comment
Gerrit-Change-Id: Ia5a7d8ae74e2286e0e9696f79c85348965ef80ed
Gerrit-PatchSet: 1
Gerrit-Project: kudu
Gerrit-Branch: master
Gerrit-Owner: Todd Lipcon <to...@apache.org>
Gerrit-Reviewer: David Ribeiro Alves <dr...@apache.org>
Gerrit-Reviewer: Kudu Jenkins
Gerrit-Reviewer: Todd Lipcon <to...@apache.org>
Gerrit-HasComments: Yes