bzr merge of a large project locally can sit for a while with no indication of what it is doing
Bug #548523 reported by
James Westby
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Confirmed
|
Medium
|
Unassigned |
Bug Description
Hi,
Take a fairly large project, say launchpad, and make two local branches inside
a shared repository, diverge them by a couple of revisions, add some fairly slow
rotational disks, and run "bzr merge". What you may find is that there is an
extended period of time where it is working, but no progress is displayed an no
messages are printed to indicate what is happening. Eventually the "preparing
file merge" phase will start.
If you don't diverge the branches then the "Nothing to do" is quick, so it's not simply
opening the branches, and not copying revision data as a shared repo is used, so
maybe it's just grabbing the graph and calculating the merge base that is slow.
Thanks,
James
tags: | added: check-for-breezy |
To post a comment you must log in.
It will help progress bugs like this if you can attach a backtrace
(press C-\ then type 'bt'), so we know where it's waiting.
thanks