public inbox for git@vger.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "D. Ben Knoble" <ben.knoble@gmail.com>
Cc: Patrick Steinhardt <ps@pks.im>,
	 Ramsay Jones <ramsay@ramsayjones.plus.com>,
	 GIT Mailing-list <git@vger.kernel.org>
Subject: Re: [RFC PATCH] test-lib: add missing prerequisites for Darwin
Date: Tue, 10 Jun 2025 08:32:28 -0700	[thread overview]
Message-ID: <xmqq8qlzobn7.fsf@gitster.g> (raw)
In-Reply-To: <CALnO6CD-2sMOkCgaucB1SYq9Cwiu4hvc-QPa9nUN=GsmozWh8g@mail.gmail.com> (D. Ben Knoble's message of "Tue, 10 Jun 2025 09:34:36 -0400")

"D. Ben Knoble" <ben.knoble@gmail.com> writes:

>> If I have some time today I will run the test suite with this patch from Junio’s tree on my (old enough to be unsupported hardware) Macbook and report back.
>>
>> D. Ben Knoble
>
> I am happy to report that my run passed (log attached). I also
> spot-checked a few test scripts that use the prereqs mentioned in the
> patch, and those executed cases with the prereqs (e.g.,
> t1700-split-index.sh exercises POSIX_PERM via 'same mode for index &
> split index'; t3700-add.sh exercises BSLASHPSPEC via "git add
> 'fo\\[ou\\]bar' ignores foobar"; t7502-commit-porcelain.sh exercises
> EXECKEEPSPID via 'a SIGTERM should break locks').
>
> All tests successful.
> Files=1023, Tests=31723, 1197 wallclock secs (13.48 usr  5.16 sys +
> 2162.62 cusr 2883.19 csys = 5064.45 CPU)
> Result: PASS
>
> Acked-by: D. Ben Knoble <ben.knoble+github@gmail.com>

Thanks.

  reply	other threads:[~2025-06-10 15:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-09 17:13 [RFC PATCH] test-lib: add missing prerequisites for Darwin Ramsay Jones
2025-06-09 18:24 ` Junio C Hamano
2025-06-09 18:41   ` Patrick Steinhardt
     [not found]     ` <9E2E7CDE-907F-40A5-8C4D-BBE57F7BA08E@gmail.com>
2025-06-10 13:34       ` D. Ben Knoble
2025-06-10 15:32         ` Junio C Hamano [this message]
2025-06-10 14:00       ` D. Ben Knoble

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqq8qlzobn7.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=ben.knoble@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=ps@pks.im \
    --cc=ramsay@ramsayjones.plus.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox