From: Ramsay Jones <ramsay@ramsayjones.plus.com>
Date: Sun, 18 Jan 2026 13:59:17 GMT
Subject: Re: Subject: [PATCH 0/2] v2.53.0-rc0 test failures on cygwin
Message-ID: <a19baa0c-e084-44c4-bd77-a6c18626a6f4@ramsayjones.plus.com>
In-Reply-To: <3f8925eb-7602-433c-83e0-a88cf8d155fa@ramsayjones.plus.com>



On 16/01/2026 8:39 pm, Ramsay Jones wrote:
> 
> 
> This cycle brings a t9700 test failure on cygwin, see patch #1.
> The second patch was owed from the last cycle, sorry about not
> getting to it sooner, but it is _still_ a puzzle. ;)
> 
> I have tested these patches on Linux without issue. On cygwin
> the t0610 test passes with '--stress' which it failed earlier
> and the t9700 test has only been tested by hand.
> 
> Directly after sending these patches, I will start a '-j8' run
> of the full testsuite on cygwin and let you know if it fails
> (it should not!). ;)

Just for avoidance of doubt, this test passed without issue:

  $ ./git version
  git version 2.53.0.rc0.2.gc56c9e3a41
  $ 

[ie. v2.53.0-rc0 + these two patches]

  $ tail test-out1
  All tests successful.
  Files=1028, Tests=32260, 2945 wallclock secs (22.75 usr 64.42 sys + 7655.90 cusr 10222.07 csys = 17965.14 CPU)
  Result: PASS
  make clean-except-prove-cache
  make[2]: Entering directory '/home/ramsay/git/t'
  rm -f -r 'chainlinttmp'
  rm -f -r 'trash directory'.*
  rm -f -r valgrind/bin
  make[2]: Leaving directory '/home/ramsay/git/t'
  make[1]: Leaving directory '/home/ramsay/git/t'
  $ 

> [When I run the testsuite like this on cygwin I can't use the
> laptop for anything else and the keyboard gets _very_ toasty!]

Now I can try a lower '-j' value to find a happy medium (although
no '-j' argument leads to approx. 4 hours for a test run, which is
already better than 6+ hours for my old laptop).

Thanks.

ATB,
Ramsay Jones