From: Jeff King <peff@peff•net>
To: git@vger•kernel.org
Subject: [PATCH 0/2] meson-windows-test ci output fixes
Date: Tue, 18 Nov 2025 04:32:21 -0500 [thread overview]
Message-ID: <20251118093221.GA530337@coredump.intra.peff.net> (raw)
I ran into a failed test a month or two ago that triggered only on the
windows-meson-test jobs. But those jobs don't actually show you any
output from the test scripts!
This is what I hacked up to improve things.
[1/2]: unit-test: ignore --no-chain-lint
[2/2]: ci(windows-meson-test): handle options and output like other test jobs
.github/workflows/main.yml | 12 +++++++++++-
ci/run-test-slice-meson.sh | 13 +++++++++++++
t/unit-tests/unit-test.c | 1 +
3 files changed, 25 insertions(+), 1 deletion(-)
create mode 100755 ci/run-test-slice-meson.sh
-Peff
next reply other threads:[~2025-11-18 9:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-18 9:32 Jeff King [this message]
2025-11-18 9:32 ` [PATCH 1/2] unit-test: ignore --no-chain-lint Jeff King
2025-11-18 9:35 ` [PATCH 2/2] ci(windows-meson-test): handle options and output like other test jobs Jeff King
2025-11-25 17:39 ` Johannes Schindelin
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=20251118093221.GA530337@coredump.intra.peff.net \
--to=peff@peff$(echo .)net \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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