From: Patrick Steinhardt <ps@pks.im>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jonathan Nieder <jrnieder@gmail.com>,
Andy Koppe <andy.koppe@gmail.com>,
git@vger.kernel.org
Subject: Re: meson-test syntax error
Date: Fri, 3 Jan 2025 07:40:17 +0100 [thread overview]
Message-ID: <Z3eGS68PkwDtBl1V@pks.im> (raw)
In-Reply-To: <xmqqr05lusvp.fsf@gitster.g>
On Thu, Jan 02, 2025 at 07:39:54AM -0800, Junio C Hamano wrote:
> Jonathan Nieder <jrnieder@gmail.com> writes:
>
> > Junio C Hamano wrote:
> >> Jonathan Nieder <jrnieder@gmail.com> writes:
> >>> Andy Koppe wrote:
> >
> >>>> make[1]: Entering directory '/src/git/t'
> >>>> rm -f -r 'test-results'
> >>>> /bin/sh: 10: Syntax error: "(" unexpected
> >>>> make[1]: *** [Makefile:119: check-meson] Error 2
> >>>>
> >>>> Due to this line:
> >>>>
> >>>> diff -u <(echo "$$meson_tests") <(echo "$$actual_tests");
> > [...]
> >>> I ran into the same today. Let's discuss in the review thread
> >>> (https://lore.kernel.org/git/20241213-pks-meson-ci-v2-5-634affccc694@pks.im/).
> >>
> >> Probably this one?
> >>
> >> <20241227-b4-pks-meson-docs-v2-11-f61e63edbfa1@pks.im>
> >
> > Ah, yes, that's the one I mean. Sorry for the noise.
>
> Sorry for being extra sloppy on this one. A patch like that with
> blatant bash-ism shouldn't have slipped the review process.
>
> One thing I had trouble with is that, with /bin/sh linked to
> /bin/bash, none of these
>
> $ SHELL=/bin/dash make test
> $ cd t && SHELL=/bin/dash make test
> $ cd t && SHELL=/bin/dash make check-meson
>
> seem to fail for me.
Sorry, as well. Thanks for the report and investigations!
Patrick
prev parent reply other threads:[~2025-01-03 6:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-02 12:17 meson-test syntax error Andy Koppe
2025-01-02 14:25 ` Jonathan Nieder
2025-01-02 14:37 ` Junio C Hamano
2025-01-02 15:22 ` Jonathan Nieder
2025-01-02 15:39 ` Junio C Hamano
2025-01-02 15:41 ` Junio C Hamano
2025-01-02 16:26 ` Junio C Hamano
2025-01-02 17:23 ` Andreas Schwab
2025-01-02 17:27 ` Junio C Hamano
2025-01-03 6:40 ` Patrick Steinhardt [this message]
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=Z3eGS68PkwDtBl1V@pks.im \
--to=ps@pks.im \
--cc=andy.koppe@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.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;
as well as URLs for NNTP newsgroup(s).