fetch fails to unlock stacked-on repositories
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Fix Released
|
Medium
|
Unassigned |
Bug Description
I was getting some weird 'UserWarning: 'LockableFiles(
BzrDir.sprout(): around line:
if source_repository is not None:
# Fetch while stacked to prevent unstacked fetch from
# Branch.sprout.
if fetch_spec is None:
else:
Before this, I checked:
result_
result_
after this fetch:
result_
result_
Now in this circumstance, the result_repo is automatically stacked, because of default stacking (the test is bzrlib.
Anyway, it leads to a very specific concern that something is taking a lock out 'on demand' but is failing to unlock it.
If it matters, this test is using a 'smart_server' branch, so it might just be buggy code in the RemoteRepository unlock code.
Related branches
Changed in bzr: | |
importance: | Undecided → Medium |
status: | New → Triaged |
Changed in bzr: | |
milestone: | none → 1.16 |
status: | Triaged → Fix Released |