{"thread":{"id":"64822","subject":"Subject: [PATCH 0/2] v2.53.0-rc0 test failures on cygwin","startedAt":"2026-01-16T20:42:31Z","lastAt":"2026-01-18T13:59:27Z","messageCount":2,"participants":["Ramsay Jones"],"isPatch":true,"patchVersion":1,"patchTotal":2},"messages":[{"id":"534086","messageId":"3f8925eb-7602-433c-83e0-a88cf8d155fa@ramsayjones.plus.com","threadId":"64822","inReplyTo":null,"subject":"Subject: [PATCH 0/2] v2.53.0-rc0 test failures on cygwin","fromName":"Ramsay Jones","fromEmail":"ramsay@ramsayjones.plus.com","sentAt":"2026-01-16T20:39:18Z","receivedAt":"2026-01-16T20:42:31Z","isPatch":true,"sender":{"key":"ramsay@ramsayjones.plus.com","avatar":"https://avatars.githubusercontent.com/u/33702710?v=4"},"body":"\n\nThis cycle brings a t9700 test failure on cygwin, see patch #1.\nThe second patch was owed from the last cycle, sorry about not\ngetting to it sooner, but it is _still_ a puzzle. ;)\n\nI have tested these patches on Linux without issue. On cygwin\nthe t0610 test passes with '--stress' which it failed earlier\nand the t9700 test has only been tested by hand.\n\nDirectly after sending these patches, I will start a '-j8' run\nof the full testsuite on cygwin and let you know if it fails\n(it should not!). ;)\n\n[When I run the testsuite like this on cygwin I can't use the\nlaptop for anything else and the keyboard gets _very_ toasty!]\n\nThanks\n\nRamsay Jones\n\nRamsay Jones (2):\n  t9700/test.pl: fix path type expectation on cygwin\n  t0610-reftable-basics: mitigate a flaky test on cygwin\n\n t/t0610-reftable-basics.sh | 2 +-\n t/t9700/test.pl            | 2 +-\n 2 files changed, 2 insertions(+), 2 deletions(-)\n\n-- \n2.52.0\n"},{"id":"534144","messageId":"a19baa0c-e084-44c4-bd77-a6c18626a6f4@ramsayjones.plus.com","threadId":"64822","inReplyTo":"3f8925eb-7602-433c-83e0-a88cf8d155fa@ramsayjones.plus.com","subject":"Re: Subject: [PATCH 0/2] v2.53.0-rc0 test failures on cygwin","fromName":"Ramsay Jones","fromEmail":"ramsay@ramsayjones.plus.com","sentAt":"2026-01-18T13:59:17Z","receivedAt":"2026-01-18T13:59:27Z","isPatch":true,"sender":{"key":"ramsay@ramsayjones.plus.com","avatar":"https://avatars.githubusercontent.com/u/33702710?v=4"},"body":"\n\nOn 16/01/2026 8:39 pm, Ramsay Jones wrote:\n> \n> \n> This cycle brings a t9700 test failure on cygwin, see patch #1.\n> The second patch was owed from the last cycle, sorry about not\n> getting to it sooner, but it is _still_ a puzzle. ;)\n> \n> I have tested these patches on Linux without issue. On cygwin\n> the t0610 test passes with '--stress' which it failed earlier\n> and the t9700 test has only been tested by hand.\n> \n> Directly after sending these patches, I will start a '-j8' run\n> of the full testsuite on cygwin and let you know if it fails\n> (it should not!). ;)\n\nJust for avoidance of doubt, this test passed without issue:\n\n  $ ./git version\n  git version 2.53.0.rc0.2.gc56c9e3a41\n  $ \n\n[ie. v2.53.0-rc0 + these two patches]\n\n  $ tail test-out1\n  All tests successful.\n  Files=1028, Tests=32260, 2945 wallclock secs (22.75 usr 64.42 sys + 7655.90 cusr 10222.07 csys = 17965.14 CPU)\n  Result: PASS\n  make clean-except-prove-cache\n  make[2]: Entering directory '/home/ramsay/git/t'\n  rm -f -r 'chainlinttmp'\n  rm -f -r 'trash directory'.*\n  rm -f -r valgrind/bin\n  make[2]: Leaving directory '/home/ramsay/git/t'\n  make[1]: Leaving directory '/home/ramsay/git/t'\n  $ \n\n> [When I run the testsuite like this on cygwin I can't use the\n> laptop for anything else and the keyboard gets _very_ toasty!]\n\nNow I can try a lower '-j' value to find a happy medium (although\nno '-j' argument leads to approx. 4 hours for a test run, which is\nalready better than 6+ hours for my old laptop).\n\nThanks.\n\nATB,\nRamsay Jones\n\n\n"}]}