From: Patrick Steinhardt <ps@pks.im>
To: Jeff King <peff@peff.net>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jun 2026, #02)
Date: Thu, 4 Jun 2026 08:52:29 +0200 [thread overview]
Message-ID: <aiEgrfVanSZzbmkI@pks.im> (raw)
In-Reply-To: <20260604062122.GB3194609@coredump.intra.peff.net>
On Thu, Jun 04, 2026 at 02:21:22AM -0400, Jeff King wrote:
> On Thu, Jun 04, 2026 at 11:35:50AM +0900, Junio C Hamano wrote:
>
> > * ps/t7527-fix-tap-output (2026-06-02) 4 commits
> > - t: let prove fail when parsing invalid TAP output
> > - t/lib-git-p4: silence output when killing p4d and its watchdog
> > - t/test-lib: silence EBUSY errors on Windows during test cleanup
> > - t7527: fix broken TAP output
> >
> > A recent regression in t7527 that broke TAP output has been fixed,
> > some other test noise that also broke TAP output has been silenced,
> > and 'prove' is now configured to fail on invalid TAP output to
> > prevent future regressions.
> >
> > Expecting a (small and hopefully final) reroll.
> > cf. <xmqqtsrlw09t.fsf@gitster.g>
> > source: <20260603-pks-t7527-fix-tap-output-v2-0-cf3af5694e20@pks.im>
>
> I guess this is the source of several CI failures on jch/seen that look
> like:
>
> Test Summary Report
> -------------------
> t7810-grep.sh (Wstat: 0 Tests: 264 Failed: 0)
> Parse errors: Unknown TAP token: "/bin/sh: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)"
>
> This happens in the dockerized jobs whose images presumably have a very
> minimal locale setup. I don't know if this is a sign that the tests have
> never been doing quite what we expect on those platforms, or if it's
> simply noise that is now being caught.
Ah, thanks for flagging. I'll investigate.
Patrick
prev parent reply other threads:[~2026-06-04 6:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-04 2:35 What's cooking in git.git (Jun 2026, #02) Junio C Hamano
2026-06-04 6:16 ` Patrick Steinhardt
2026-06-04 6:21 ` Jeff King
2026-06-04 6:52 ` 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=aiEgrfVanSZzbmkI@pks.im \
--to=ps@pks.im \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
/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