From: Patrick Steinhardt <ps@pks.im>
To: Junio C Hamano <gitster@pobox.com>
Cc: 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: Mon, 9 Jun 2025 20:41:50 +0200 [thread overview]
Message-ID: <aEcq7sbPx57r-qKK@pks.im> (raw)
In-Reply-To: <xmqq8qm0srh3.fsf@gitster.g>
On Mon, Jun 09, 2025 at 11:24:40AM -0700, Junio C Hamano wrote:
> Ramsay Jones <ramsay@ramsayjones.plus.com> writes:
>
> > commit d3d8c601fd ("t7815: fix unexpectedly passing test on macOS",
> > 2025-06-02) added a MACOS prerequisite by adding a 'Darwin' case
> > label to the 'OS-specific' case statement. However, this commit
> > forgot to set several prerequisites which appear in the 'default'
> > case label, in addition to the new MACOS prerequisite. This causes
> > several tests, which macOS should pass, being skipped.
> >
> > In order to run all applicable tests on macOS, add the missing
> > prerequisites to the 'Darwin' case.
> >
> > Signed-off-by: Ramsay Jones <ramsay@ramsayjones.plus.com>
> > ---
> >
> > Hi Junio, Patrick,
> >
> > I was looking at something else when I noticed this ... but I can't test
> > this, since I don't have access to a macOS system (indeed I can't confirm
> > that is actually a problem, but lots of tests should be being skipped! ;) ).
> >
> > I initially deleted the 'Darwin' case and set the MACOS prerequisite after
> > the case statement - which may be a better solution. dunno.
> >
> > I marked this RFC because I can't test this. Hint, Hint ...
> >
> > Note, commit d3d8c601fd is only in next. If this is not going to be
> > part of the release, then this (or something similar) could be squashed
> > into it when the next branch is re-wound.
> >
> > Thanks.
>
> I do not have access to a macOS system either, but the change in
> this patch seems like a very safe and sane thing to do; it will
> bring us back to the state before that problematic commit with
> respect to these three prerequisites.
>
> Let me queue it on top of ps/meson-tap-parse topic.
Yup, that change looks reasonable to me, as well. I cannot test it right
now though as I'm on vacation until the end of June, so I ain't got
access to any macOS devices right now.
Patrick
next prev parent reply other threads:[~2025-06-09 18:41 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 [this message]
[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
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=aEcq7sbPx57r-qKK@pks.im \
--to=ps@pks.im \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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