From: Jeff King <peff@peff.net>
To: Patrick Steinhardt <ps@pks.im>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH v3 5/8] t7810: turn MB_REGEX check into a lazy prereq
Date: Mon, 8 Jun 2026 21:22:36 -0400 [thread overview]
Message-ID: <20260609012236.GA1502349@coredump.intra.peff.net> (raw)
In-Reply-To: <20260604-pks-t7527-fix-tap-output-v3-5-7d766ed481e4@pks.im>
On Thu, Jun 04, 2026 at 12:07:35PM +0200, Patrick Steinhardt wrote:
> diff --git a/t/t7810-grep.sh b/t/t7810-grep.sh
> index 1b195bee59..d61c4a4d73 100755
> --- a/t/t7810-grep.sh
> +++ b/t/t7810-grep.sh
> @@ -18,8 +18,9 @@ test_invalid_grep_expression() {
> '
> }
>
> -LC_ALL=en_US.UTF-8 test-tool regex '^.$' '¿' &&
> - test_set_prereq MB_REGEX
> +test_lazy_prereq MB_REGEX '
> + LC_ALL=en_US.UTF-8 test-tool regex "^.$" "¿"
> +'
Oh good. Since the error was coming from the shell, I was worried that
the use of LC_ALL inside the test snippets was somehow causing output to
leak to stderr. But it was just (yet another) case where we ran a tool
outside of a snippet, which is easy to fix.
This also allays my fears that the tests might have been misbehaving on
those other platforms. They are (and were) caught by this prereq and not
run at all, which is the right thing.
Thanks for fixing.
-Peff
next prev parent reply other threads:[~2026-06-09 1:22 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-02 8:54 [PATCH 0/4] t: fix broken TAP output Patrick Steinhardt
2026-06-02 8:54 ` [PATCH 1/4] t7527: " Patrick Steinhardt
2026-06-02 8:54 ` [PATCH 2/4] t/test-lib: silence EBUSY errors on Windows during test cleanup Patrick Steinhardt
2026-06-02 8:54 ` [PATCH 3/4] t/lib-git-p4: silence output when killing p4d and its watchdog Patrick Steinhardt
2026-06-02 9:32 ` Junio C Hamano
2026-06-02 10:20 ` Patrick Steinhardt
2026-06-02 13:16 ` Junio C Hamano
2026-06-02 8:54 ` [PATCH 4/4] t: let prove fail when parsing invalid TAP output Patrick Steinhardt
2026-06-03 5:39 ` [PATCH v2 0/4] t: fix broken " Patrick Steinhardt
2026-06-03 5:39 ` [PATCH v2 1/4] t7527: " Patrick Steinhardt
2026-06-03 5:39 ` [PATCH v2 2/4] t/test-lib: silence EBUSY errors on Windows during test cleanup Patrick Steinhardt
2026-06-03 5:39 ` [PATCH v2 3/4] t/lib-git-p4: silence output when killing p4d and its watchdog Patrick Steinhardt
2026-06-03 5:39 ` [PATCH v2 4/4] t: let prove fail when parsing invalid TAP output Patrick Steinhardt
2026-06-04 10:07 ` [PATCH v3 0/8] t: fix broken " Patrick Steinhardt
2026-06-04 10:07 ` [PATCH v3 1/8] gitlab-ci: rearrange Linux jobs to match GitHub's order Patrick Steinhardt
2026-06-04 10:07 ` [PATCH v3 2/8] gitlab-ci: add missing Linux jobs Patrick Steinhardt
2026-06-04 10:07 ` [PATCH v3 3/8] ci: unify Linux images across GitLab and GitHub Patrick Steinhardt
2026-06-04 10:07 ` [PATCH v3 4/8] t7527: fix broken TAP output Patrick Steinhardt
2026-06-04 10:07 ` [PATCH v3 5/8] t7810: turn MB_REGEX check into a lazy prereq Patrick Steinhardt
2026-06-09 1:22 ` Jeff King [this message]
2026-06-04 10:07 ` [PATCH v3 6/8] t/test-lib: silence EBUSY errors on Windows during test cleanup Patrick Steinhardt
2026-06-04 10:07 ` [PATCH v3 7/8] t/lib-git-p4: silence output when killing p4d and its watchdog Patrick Steinhardt
2026-06-04 10:07 ` [PATCH v3 8/8] t: let prove fail when parsing invalid TAP output Patrick Steinhardt
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=20260609012236.GA1502349@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=ps@pks.im \
/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