diff options
| author | W. Trevor King <wking@drexel.edu> | 2010-12-06 10:12:57 -0500 |
|---|---|---|
| committer | W. Trevor King <wking@drexel.edu> | 2010-12-06 10:13:01 -0500 |
| commit | ef0a5537747a2e5a0b2248018e981f80ae0b0f9f (patch) | |
| tree | 832ccf487812e8ccf03ab8fe47c0950a0db3ee8b /.be/bea86499-824e-4e77-b085-2d581fa9ccab/bugs/04edb940-06dd-4ded-8697-156d54a1d875/comments/e3389187-1e84-43d5-b40b-26f53090edff | |
| parent | 22dd202ff4c0a1893f6e9f4d2b6aa1d4da3bf728 (diff) | |
| download | bugseverywhere-ef0a5537747a2e5a0b2248018e981f80ae0b0f9f.tar.gz | |
Run cmd.cleanup_now() after executing bzr commands.
Otherwise
be remove ...
blocks if it needs to remove multiple files, since
bzrlib.builtins.cmd_remove needs write locks, and the second remove
will try to aquire the lock that the first aquire hadn't released. If
we force the release, the lock will be available for the second (and
later) removal.
It's not a problem to call cleanup_now() too often, because calling it
clears the cleanup command stack, so I just added explicit cleanups
after every bzr .run() call.
Diffstat (limited to '.be/bea86499-824e-4e77-b085-2d581fa9ccab/bugs/04edb940-06dd-4ded-8697-156d54a1d875/comments/e3389187-1e84-43d5-b40b-26f53090edff')
0 files changed, 0 insertions, 0 deletions