Rev 4526: Having a write lock should block a read lock and vice-versa. in http://bazaar.launchpad.net/~jameinel/bzr/1.18-lock-warnings

[John Arbash Meinel]

At http://bazaar.launchpad.net/~jameinel/bzr/1.18-lock-warnings

------------------------------------------------------------
revno: 4526
revision-id: john at arbash-meinel.com-20090710200724-hq5ls63lxocfaiu0
parent: john at arbash-meinel.com-20090710180043-mxzzfl69nh2biwvf
committer: John Arbash Meinel <john at arbash-meinel.com>
branch nick: 1.18-lock-warnings
timestamp: Fri 2009-07-10 15:07:24 -0500
message:
  Having a write lock should block a read lock and vice-versa.
-------------- next part --------------
=== modified file 'bzrlib/tests/test_lock.py'
--- a/bzrlib/tests/test_lock.py	2009-07-10 18:00:43 +0000
+++ b/bzrlib/tests/test_lock.py	2009-07-10 20:07:24 +0000
@@ -78,6 +78,15 @@
         finally:
             r_lock.unlock()
 
+    def test_write_locks_block_read_lock(self):
+        w_lock = self.write_lock('a-lock-file')
+        try:
+            self.assertRaises(errors.LockContention,
+                              self.read_lock, 'a-lock-file')
+        finally:
+            w_lock.unlock()
+
+
     def test_temporary_write_lock(self):
         r_lock = self.read_lock('a-lock-file')
         try: