Re: [BUG] commit fails with 'bus error' when working directory is on an NFS share

From: Jeff King <peff@peff.net>
Date: Dec 1, 2024, 21:36 UTC
Message-ID: <20241201213636.GB145938@coredump.intra.peff.net>
In-Reply-To: <CAJ-DG_CNPGgfafyTcKWYeNXHD4gsspWakzQoRhfggMqZjenkyg@mail.gmail.com>

On Sun, Dec 01, 2024 at 10:17:44AM -0700, Dmitriy Panteleyev wrote:

Show 13 quoted lines

> > > I attempted to upgrade git to v2.47.1, with the same result.
> > >
> > > I then downgraded git to v2.34.1 (the version for the previous
> > > distribution release) and the error has resolved.
> >
> > Can you try bisecting between v2.34.1 and v2.43.0 to see which commit
> > introduces the problem for you?
> >
> > -Peff
> 
> Bisecting: 0 revisions left to test after this (roughly 0 steps)
> [04fb96219abc0cbe46ba084997dc9066de3ac889] parse_object(): drop extra
> "has" check before checking object type

That seems like an unlikely commit to introduce the problem you're seeing. And how did we end up with 0 revisions left to check, but no final outcome? Did you need to do one more test and "git bisect good/bad" on this commit?

Or alternatively, can you share what you're doing to test the bisection? That might help us reproduce. I kind of wonder if the results might not be deterministic, to end up at an apparently unrelated commit like that.

-Peff