git/list[1] front-page[2] threads[3] people[4] search[5] about
 

'Failed to create .git/index.lock'

From
Andreas Krey <a.krey@gmx.de>
Date
Feb 9, 2016, 07:58 UTC
Message-ID
<20160209075829.GA12331@inner.h.apk.li>
Hi all,

I have a single workspace where executing merges occasionally leads to a left-over .git/index.lock file that prevents me from adding resolved conflicted files.

I'm running a sped-up integration/feature branch process, and the merges and conflict resolution are automated. But the index.lock thing is happening only in one repo of the three that are doing this.

Any hints as to debugging this?

(It is not a running background gc, the lock file is still around when there is nothing running any more, for hours.)

Andreas
-- 
"Totally trivial. Famous last words."
From: Linus Torvalds <torvalds@*.org>
Date: Fri, 22 Jan 2010 07:29:21 -0800
Next: Lars Schneider
Message 1 of 3 in “'Failed to create .git/index.lock'”
  1. Andreas KreyFeb 9, 2016
  2. Lars SchneiderFeb 15, 2016
  3. Andreas KreyFeb 15, 2016

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.