RE: Issues with t7519.19, was RE: [Breakage] 2.22.0-rc1 t5401-update-hooks.sh
- Date: Thu, 23 May 2019 22:55:18 +0200 (CEST)
- From: Johannes Schindelin <Johannes.Schindelin@xxxxxx>
- Subject: RE: Issues with t7519.19, was RE: [Breakage] 2.22.0-rc1 t5401-update-hooks.sh
On Thu, 23 May 2019, Randall S. Becker wrote:
> On May 23, 2019 16:06, Johannes Schindelin wrote:
> > On Wed, 22 May 2019, Randall S. Becker wrote:
> > > On May 21, 2019 20:48, brian m. carlson wrote:
> > > > To: Randall S. Becker <rsbecker@xxxxxxxxxxxxx>
> > > > Cc: 'Git Mailing List' <git@xxxxxxxxxxxxxxx>
> > > > 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?
> > >
> > > I will give it a go. Having exactly the same behaviour in t7519
> > > subtest 19. I wonder whether there are breadcrumbs not being cleaned
> > > up. Will report back when I am able - may take a day or so.
> > I fear that t7519's problems are *completely* unrelated to the t5401 issue
> > you reported earlier. I hunted the t7519 problems down today, and I could
> > imagine that these patches fix your t7519, too:
> > https://github.com/gitgitgadget/git/pull/223
> From the description, I believe it. Timestamp resolution on NonStop is in microseconds and those are not even slightly simulated. Coupled with this being an MPP not SMP, things can occur within the same microsecond, or in weird situations slightly before or after when comparing the clock on different CPUs. Yes, time-travel is possible at the single microsecond level 😉. Cores are synchronized, but our machine has 4 CPUs and synchronizing the file system across all of them does lead to slightly strange situations.
I tested my patches with
sh t7519-status-fsmonitor.sh --stress-jobs=8 --stress-limit=10
Why don't you check out my branch, build and test, and then we know
whether it fixes your t7519 bug?