bug#80903: 31.0.50; vc-next-action fails irregularly for git

Version: 31.1

Philip Kaludercic [25/Apr 12:02pm GMT] wrote:
> I have been experiencing this issue regularly for a few weeks now but
> haven't managed to pin-point the cause.  Sometimes when trying to commit
> a change, the Git process fails with this error message:
>
> --8<---------------cut here---------------start------------->8---
> Running 'git commit -m "..." --only -- file1 file2'...
> fatal: Unable to create '/path/to/repo/.git/index.lock': File exists.
>
> Another git process seems to be running in this repository, e.g.
> an editor opened by 'git commit'. Please make sure all processes
> are terminated then try again. If it still fails, a git process
> may have crashed in this repository earlier:
> remove the file manually to continue.
> Finished in 0.01 seconds
> --8<---------------cut here---------------end--------------->8---
>
> Upon checking, this lock file never exists.  If I copy the command and
> execute it by hand the commit always goes through.  As this occurs
> irregularly I feel like we are dealing with a race condition.
>
> (Annoyingly I only run into the issue when trying to solve some other
> problem that has priority in that moment, which is why I have been
> living with it for a while now.)
>
> I am not sure if this is related to bug#76187.

I think I've fixed this now.  Optimistically closing the bug.

-- 
Sean Whitton