RE: [Breakage] 2.22.0-rc1 t5401-update-hooks.sh

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: May 23, 2019, 21:00 UTC
Message-ID: <nycvar.QRO.7.76.6.1905232258280.46@tvgsbejvaqbjf.bet>
In-Reply-To: <004e01d511a1$c521a120$4f64e360$@nexbridge.com>

Hi Randall,

On Thu, 23 May 2019, Randall S. Becker wrote:

Show 19 quoted lines

> On May 21, 2019 20:48, brian m. carlson wrote:
> > To: Randall S. Becker <rsbecker@nexbridge.com>
> > Cc: 'Git Mailing List' <git@vger.kernel.org>
> > Subject: Re: [Breakage] 2.22.0-rc1 t5401-update-hooks.sh
> >
> > On 2019-05-21 at 21:47:54, Randall S. Becker wrote:
> > > When running the test in isolation, it passes without incident
> > > whether or not --verbose is used. So far, this only occurs on the
> > > first run through. I wanted to report it, based on the inconsistency
> > > of results. This is not the first time tests have acted in this
> > > fashion, and I realize it is difficult to do anything about it
> > > without being able to recreate
> > the situation.
> >
> > Does running git clean -dxf cause it to be reproducible?
>
> Made no difference. t5401 passed cleanly after a the clean -dxf. I don't
> know where the breadcrumbs are. I guess it could be something funky in
> the file system on platform or with bash.

FWIW I do not see any of the major platforms having any sort of regression in t5401: https://dev.azure.com/gitgitgadget/git/_test/analytics?definitionId=4&contextType=build

So I guess the only way you will find out more about this issue is by instrumenting the code and digging in. You will most likely find that the `--stress` mode will help you recreate the situation rather easily.

Ciao, Johannes