Fix tokudb.hotindex-insert-bigchar failure in buildbot.

This test needs at least 320M for tokudb-max-lock-memory. Normally tokudb-max-lock-memory is auto-sized to be 1/16th of the available RAM size, and many our test VMs have 4G of RAM.

Fix tokudb.hotindex-insert-bigchar failure in buildbot.
This test needs at least 320M for tokudb-max-lock-memory. Normally tokudb-max-lock-memory is auto-sized to be 1/16th of the available RAM size, and many our test VMs have 4G of RAM.
47b615d8 · Sergei Golubchik · e68bccc7 · 47b615d8
Commit 47b615d8 authored Dec 15, 2013 by Sergei Golubchik
Hide whitespace changes
Inline Side-by-side

Showing with 1 addition and 0 deletions

storage/tokudb/mysql-test/tokudb/t/hotindex-insert-bigchar.opt ...ge/tokudb/mysql-test/tokudb/t/hotindex-insert-bigchar.opt +1 -0

No files found.
--- a/storage/tokudb/mysql-test/tokudb/t/hotindex-insert-bigchar.opt
+++ b/storage/tokudb/mysql-test/tokudb/t/hotindex-insert-bigchar.opt
+--loose-tokudb-max-lock-memory=320M