/breezy/unstable

To get this branch, use:
bzr branch https://code.breezy-vcs.org/breezy/unstable

« back to all changes in this revision

Viewing changes to breezy/tests/blackbox/test_break_lock.py

  • Committer: Jelmer Vernooij
  • Date: 2017-05-24 01:39:33 UTC
  • mfrom: (3815.3776.6)
  • Revision ID: jelmer@jelmer.uk-20170524013933-ir4y4tqtrsiz2ka2
New upstream snapshot.

Show diffs side-by-side

added added

removed removed

Lines of Context:
16
16
 
17
17
"""Tests for lock-breaking user interface"""
18
18
 
19
 
from bzrlib import (
 
19
from breezy import (
20
20
    branch,
21
21
    config,
22
22
    controldir,
24
24
    osutils,
25
25
    tests,
26
26
    )
27
 
from bzrlib.tests.matchers import ContainsNoVfsCalls
28
 
from bzrlib.tests.script import (
 
27
from breezy.tests.matchers import ContainsNoVfsCalls
 
28
from breezy.tests.script import (
29
29
    run_script,
30
30
    )
31
31
 
33
33
class TestBreakLock(tests.TestCaseWithTransport):
34
34
 
35
35
    # General principal for break-lock: All the elements that might be locked
36
 
    # by a bzr operation on PATH, are candidates that break-lock may unlock.
 
36
    # by a brz operation on PATH, are candidates that break-lock may unlock.
37
37
    # so pathologically if we have a lightweight checkout A, of branch B, which
38
38
    # is bound to location C, the following things should be checked for locks
39
39
    # to break:
73
73
        """With --force, the user isn't asked for confirmation"""
74
74
        self.master_branch.lock_write()
75
75
        run_script(self, """
76
 
        $ bzr break-lock --force master-repo/master-branch
 
76
        $ brz break-lock --force master-repo/master-branch
77
77
        Broke lock ...master-branch/.bzr/...
78
78
        """)
79
79
        # lock should now be dead