From 6bfe82f5a292e7bdd2f2201dce222f5845d199b4 Mon Sep 17 00:00:00 2001
From: keleher <keleher@cs.umd.edu>
Date: Sun, 24 Nov 2019 17:38:33 -0500
Subject: [PATCH] auto

---
 README.md | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index 6fb5496..4992f63 100644
--- a/README.md
+++ b/README.md
@@ -102,8 +102,9 @@ You can use `testingLocks.py` as the basis for your testing. The provided versio
 
 Note that you should modify this test (change the transaction, or create a new one) such that it tests tuple locks as discussed above. This test works fine w/ tuple locks defaulting to table locks, but our tests will not.
 
-We will test locks by running transactions that delay through `sleep`s. We will use timing
-effects to ensure that your locks are conflicting when necessary, and not when not.
+We will test locks by running transactions that delay through `sleep`s and use timing
+effects to ensure that your locks are conflicting when necessary, and not when not. We
+will also check for the lock messages ("able to get this lock on...", etc.).
 
 
 **Recovery**
-- 
GitLab