Mercurial stuck “waiting for lock”

Question

Got a bluescreen in windows while cloning a mercurial repository.

After reboot, I now get this message for almost all hg commands:

c:\\src\\>hg commit
wai         


        

Answer 1

I encountered this problem on Mac OS X 10.7.5 and Mercurial 2.6.2 when trying to push. After upgrading to Mercurial 3.2.1, I got "no changes found" instead of "waiting for lock on repository". I found out that somehow the default path had gotten set to point to the same repository, so it's not too surprising that Mercurial would get confused.

Answer 2

If it only happens on mapped drives it might be bug https://bitbucket.org/tortoisehg/thg/issue/889/cant-commit-file-over-network-share. Using UNC path instead of drive letter seems to sidestep the issue.

Answer 3

When waiting for lock on working directory, delete .hg/wlock.

Answer 4

I had the same problem on Win 7. The solution was to remove following files:

1. .hg/store/phaseroots
2. .hg/wlock

As for .hg/store/lock - there was no such file.

Answer 5

Coworker had this exact problem today, after a BSoD while trying to push. He had to:

• delete the file .hg/store/lock (as per the accepted answer)
• delete the file .hg/store/phaseroots (as per this TortoiseHG bug report)

Then his repo worked again.

EDIT: As per @Marmoute's comment - when dealing with lock-related issues, using hg debuglock is a safer alternative to blindly deleting the .hg/store/lock file.