From: Taylor Blau <me@ttaylorr.com>
To: Kristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>
Cc: git@vger.kernel.org, Kristoffer Haugsbakk <code@khaugsbakk.name>,
Junio C Hamano <gitster@pobox.com>,
Dragan Simic <dsimic@manjaro.org>
Subject: Re: [PATCH v2] t7001: add failure test which triggers assertion
Date: Mon, 21 Oct 2024 17:29:11 -0400 [thread overview]
Message-ID: <ZxbHp9ndCIWj14xH@nand.local> (raw)
In-Reply-To: <1f3b62bb-7c3a-4bac-8995-8df417228ed2@app.fastmail.com>
On Mon, Oct 21, 2024 at 11:25:26PM +0200, Kristoffer Haugsbakk wrote:
> 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
next prev parent reply other threads:[~2024-10-21 21:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-05 17:41 [BUG] mv: can trigger assertion failure with three parameters (builtin/mv.c:481) Kristoffer Haugsbakk
2024-01-05 18:52 ` Junio C Hamano
2024-01-05 19:06 ` Dragan Simic
2024-02-18 12:42 ` Kristoffer Haugsbakk
2024-10-20 22:14 ` [PATCH v2] t7001: add failure test which triggers assertion kristofferhaugsbakk
2024-10-21 21:21 ` Taylor Blau
2024-10-21 21:25 ` Kristoffer Haugsbakk
2024-10-21 21:29 ` Taylor Blau [this message]
2024-10-22 21:14 ` [PATCH v3] " kristofferhaugsbakk
2024-10-23 20:36 ` Taylor Blau
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZxbHp9ndCIWj14xH@nand.local \
--to=me@ttaylorr.com \
--cc=code@khaugsbakk.name \
--cc=dsimic@manjaro.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=kristofferhaugsbakk@fastmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).