From 9afbacef2758223ba3190b459fcf794c7cc855e5 Mon Sep 17 00:00:00 2001
From: "Andrew M. Kuchling" <amk@amk.ca>
Date: Mon, 26 Jun 2006 13:23:10 +0000
Subject: [PATCH] Add a test for a conflicting lock.

On slow machines, maybe the time intervals (2 sec, 0.5 sec) will be too tight.
I'll see how the buildbots like it.
---
 Lib/test/test_mailbox.py | 22 ++++++++++++++++++++++
 1 file changed, 22 insertions(+)

diff --git a/Lib/test/test_mailbox.py b/Lib/test/test_mailbox.py
index 914a20c2ba2..ad25404424e 100644
--- a/Lib/test/test_mailbox.py
+++ b/Lib/test/test_mailbox.py
@@ -720,6 +720,28 @@ class _TestMboxMMDF(TestMailbox):
         self.assert_(contents == open(self._path, 'rb').read())
         self._box = self._factory(self._path)
 
+    def test_lock_conflict(self):
+        # Fork off a subprocess that will lock the file for 2 seconds,
+        # unlock it, and then exit.
+        pid = os.fork()
+        if pid == 0:
+            # In the child, lock the mailbox.
+            self._box.lock()
+            time.sleep(2)
+            self._box.unlock()
+            os._exit(0)
+
+        # In the parent, sleep a bit to give the child time to acquire
+        # the lock.
+        time.sleep(0.5)
+        self.assertRaises(mailbox.ExternalClashError,
+                          self._box.lock)
+        
+        # Wait for child to exit.  Locking should now succeed.
+        pid, status = os.wait()
+        self._box.lock()
+        self._box.unlock()
+        
 
 class TestMbox(_TestMboxMMDF):