git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH 0/2] meson-windows-test ci output fixes

From
Jeff King <peff@peff.net>
Date
Nov 18, 2025, 09:32 UTC
Message-ID
<20251118093221.GA530337@coredump.intra.peff.net>

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: Jeff King
Message 1 of 4 in “meson-windows-test ci output fixes”
  1. 0/2 meson-windows-test ci output fixesJeff King, Nov 18, 2025
  2. 1/2 unit-test: ignore --no-chain-lintJeff King, Nov 18, 2025
  3. 2/2 ci(windows-meson-test): handle options and output like other test jobsJeff King, Nov 18, 2025
  4. Johannes SchindelinNov 25, 2025

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.