Re: [PATCH v2] t7001: add failure test which triggers assertion
- From
Taylor Blau <me@ttaylorr.com>
- Date
- Oct 21, 2024, 21:29 UTC
- Message-ID
- <ZxbHp9ndCIWj14xH@nand.local>
- In-Reply-To
- <1f3b62bb-7c3a-4bac-8995-8df417228ed2@app.fastmail.com>
On Mon, Oct 21, 2024 at 11:25:26PM +0200, Kristoffer Haugsbakk wrote:
Show 24 quoted lines
> On Mon, Oct 21, 2024, at 23:21, Taylor Blau wrote: > > On Mon, Oct 21, 2024 at 12:14:46AM +0200, > > kristofferhaugsbakk@fastmail.com wrote: > >> From: Kristoffer Haugsbakk <code@khaugsbakk.name> > >> > >> git-mv(1) gets very confused: > >> > >> git: builtin/mv.c:506: cmd_mv: Assertion `pos >= 0' failed. > >> Aborted (core dumped) > >> test_must_fail: died by signal 6: git mv a/a.txt a b > >> fatal: Unable to create '<path>.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. > > > > There was some good analysis of what the problem was in the earlier > > parts of this thread. I think it is probably worth capturing some of > > those here, too. > > I will try to incorporate Junio’s analysis into the commit message > tomorrow. :)
Thanks, I look forward to it!
Thanks, Taylor