Browse Source

tests: fix mutex test on win32 where mutexes are always reentrant

rdb 7 years ago
parent
commit
1a94e65b17
1 changed files with 8 additions and 2 deletions
  1. 8 2
      tests/pipeline/test_mutex.py

+ 8 - 2
tests/pipeline/test_mutex.py

@@ -6,7 +6,7 @@ def test_mutex_acquire_release():
     m.acquire()
 
     # Assert that the lock is truly held now
-    assert not m.try_acquire()
+    assert m.debug_is_locked()
 
     # Release the lock
     m.release()
@@ -25,7 +25,7 @@ def test_mutex_try_acquire():
     assert m.try_acquire()
 
     # Assert that the lock is truly held now
-    assert not m.try_acquire()
+    assert m.debug_is_locked()
 
     # Clean up
     m.release()
@@ -45,9 +45,15 @@ def test_remutex_try_acquire():
     # Trying to acquire the lock should succeed
     assert m.try_acquire()
 
+    # Should report being locked
+    assert m.debug_is_locked()
+
     # Trying a second time should succeed
     assert m.try_acquire()
 
+    # Should still report being locked
+    assert m.debug_is_locked()
+
     # Clean up
     m.release()
     m.release()