When I unlock a DirectBranchCommit in my tests without committing first, bzrlib tells me the lock was broken while still open.
Error in test lp.code.tests.test_directbranchcommit.TestDirectBranchCommit.test_DirectBranchCommit_aborts_cleanly
Traceback (most recent call last):
File "/home/jtv/canonical/lp-branches/bug-402067/lib/lp/testing/__init__.py", line 332, in run
self.tearDown()
File "/home/jtv/canonical/lp-branches/bug-402067/lib/lp/code/tests/test_directbranchcommit.py", line 47, in tearDown
self.committer.unlock()
File "/home/jtv/canonical/lp-branches/bug-402067/lib/lp/code/model/directbranchcommit.py", line 186, in unlock
self.bzrbranch.unlock()
File "/home/jtv/canonical/lp-sourcedeps/eggs/bzr-1.17rc1-py2.4-linux-i686.egg/bzrlib/branch.py", line 2124, in unlock
self.control_files.unlock()
File "/home/jtv/canonical/lp-sourcedeps/eggs/bzr-1.17rc1-py2.4-linux-i686.egg/bzrlib/lockable_files.py", line 318, in unlock
self._lock.unlock()
File "/home/jtv/canonical/lp-sourcedeps/eggs/bzr-1.17rc1-py2.4-linux-i686.egg/bzrlib/lockdir.py", line 308, in unlock
self.confirm()
File "/home/jtv/canonical/lp-sourcedeps/eggs/bzr-1.17rc1-py2.4-linux-i686.egg/bzrlib/lockdir.py", line 407, in confirm
raise LockBroken(self)
LockBroken: Lock was broken while still open: LockDir(chroot-241497484:///~person-name21/product-name16/branch23/.bzr/branch/lock) - check storage consistency!
Retargeting to 3.0, which is the new name for 2.2.9. Haven't renamed the milestone as the 3.0 milestone is in a different series.