[Commits] a174d6a3e8e: Don't run rocksdb.locking_issues in range-locking mode as its tests assume point locks

Sergei Petrunia psergey at askmonty.org
Mon Jan 7 18:55:46 EET 2019


revision-id: a174d6a3e8e6fdc0d63268ede3a949f64b86baa0 (fb-prod201801-187-ga174d6a3e8e)
parent(s): a49400fed3292fa3e2dde4215f50c58bd4d6b342
author: Sergei Petrunia
committer: Sergei Petrunia
timestamp: 2019-01-07 19:55:46 +0300
message:

Don't run rocksdb.locking_issues in range-locking mode as its tests assume point locks

---
 mysql-test/suite/rocksdb/t/locking_issues.test | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/mysql-test/suite/rocksdb/t/locking_issues.test b/mysql-test/suite/rocksdb/t/locking_issues.test
index 035046ae368..95a6676f78a 100644
--- a/mysql-test/suite/rocksdb/t/locking_issues.test
+++ b/mysql-test/suite/rocksdb/t/locking_issues.test
@@ -1,5 +1,8 @@
 --source include/have_rocksdb.inc
 
+# A lot of tests below assume point locking, not range.
+--source suite/rocksdb/include/not_range_locking.inc
+
 let $isolation_level = REPEATABLE READ;
 --source suite/rocksdb/include/locking_issues_case1_1.inc
 


More information about the commits mailing list