Extend lock error for not owned special case

Using the locking routines, it is useful to be able to
distingush a generic lock error from a one that is related
to the lock not being owned anymore (without doing string
checks); this allows say a lock extension thread to attempt
to re-acquire the lock in this case (vs just dying).

1 files changed, 4 insertions, 4 deletions

diff --git a/tests/test_lock.py b/tests/test_lock.py
index a6adbc2..5ad7d5c 100644
--- a/tests/test_lock.py
+++ b/tests/test_lock.py
@@ -1,7 +1,7 @@
 import pytest
 import time
 
-from redis.exceptions import LockError
+from redis.exceptions import LockError, LockErrorNotOwned
 from redis.lock import Lock
 
 
@@ -85,7 +85,7 @@ class TestLock(object):
         lock.acquire(blocking=False)
         # manually change the token
         r.set('foo', 'a')
-        with pytest.raises(LockError):
+        with pytest.raises(LockErrorNotOwned):
             lock.release()
         # even though we errored, the token is still cleared
         assert lock.local.token is None
@@ -119,10 +119,10 @@ class TestLock(object):
         lock.release()
 
     def test_extending_lock_no_longer_owned_raises_error(self, r):
-        lock = self.get_lock(r, 'foo')
+        lock = self.get_lock(r, 'foo', timeout=10)
         assert lock.acquire(blocking=False)
         r.set('foo', 'a')
-        with pytest.raises(LockError):
+        with pytest.raises(LockErrorNotOwned):
             lock.extend(10)