Error during switch leaves pending merge

Bug #917575 reported by Gerard Krol
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Bazaar
Expired
Undecided
Unassigned
Bazaar Explorer
Incomplete
Undecided
Unassigned

Bug Description

When switching to other branches we often encounter the following error:
bzr: ERROR: Could not acquire lock "C:/somedirectory/.bzr/checkout/dirstate"
This occurs on all versions of windows and both on 32/64 bit.

Would not be a problem if we would just have to click retry but that's not possible this leaves a pending merge behind. We then have to whack bazaar with "bzr revert" "bzr update" "bzr revert" and then try to switch again.

It would be great if the lock problem could be fixed (just try again?) AT LEAST leave the tree the way it was before the switch command because everyone is getting massively confused about what is going on and if any commits are lost.

Revision history for this message
Martin Packman (gz) wrote :

Thanks for the report. It's not completely clear to me what circumstances you're hitting the locking issue, is it under bzr-explorer only of with switch from the command line as well? Do you sometimes see the problem reported as bug 901104 or only the lock error? An extract of your .bzr.log from a switch that fails would be helpful, but to make progress we really need to find out what has the dirstate file open. If you're familiar with a debugging tool or something like Process Explorer finding out which process are involved may be start.

Changed in bzr:
status: New → Incomplete
Revision history for this message
Gerard Krol (gerard-) wrote :

It's not clear to me either what causes this. It seems the lock is only held for a very short time, because I don't have to terminate any process and can try the switch again after the revert update dance.

I've never seen the error from bug #901104.

I want to note again that I don't really care about the fact that the operation fails with an error about a lock. It's the fact that the state of the working tree get's screwed up that's the real problem.

I've attached the log from a failed switch and a subsequent click on retry (where it reports the tree is out of date).

Revision history for this message
Gerard Krol (gerard-) wrote :
Revision history for this message
Alexander Belchenko (bialix) wrote :

Can you test the latest bzr-explorer 1.2.2 and tell us whether you still experience such problems?

Changed in bzr-explorer:
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Bazaar because there has been no activity for 60 days.]

Changed in bzr:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.