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

Re: Expected test suite behavior

From
Jeff King <peff@peff.net>
Date
May 25, 2026, 07:27 UTC
Message-ID
<20260525072711.GE2737798@coredump.intra.peff.net>
In-Reply-To
<CAC2QwmKgQW2c6_OhepsB1hzXYHxpX0X4eyQS0dPcxRZLOnCdig@mail.gmail.com>
On Sun, May 24, 2026 at 11:20:54PM -0700, Michael Montalbo wrote:
Show 11 quoted lines
> Amogh Dambal <amoghdambal1@gmail.com> writes:
> > Hey folks,
> >
> > I wanted to get started hacking on/poking around the Git source, but I'm
> > seeing some behavior with the tests that I can't quite figure out.
> > [...]
> > Is there a README/documentation I've missed reading that can help
> > explain the behavior I'm seeing?
> 
> Hello. If you run `make test GIT_TEST_OPTS=--verbose` or uncomment
> L16 of t/Makefile is there more information describing the issue?

You can't use --verbose when running under the "prove" TAP harness (which the OP seems to be doing). You can use --verbose-log instead, and then output is in t/test-results/t1234-whatever.out.

However, when debugging tests I find it easier to focus on a single failing test by running it individually, like:

  cd t
  ./t1234-whatever.sh -v -i -x

That will stop at the first failure (-i), showing the output of all commands (-v), and additionally enabling shell tracing (-x) so you can see which command in the test failed.

-Peff
Previous: Michael MontalboNext: Amogh Dambal
Message 2 of 7 in “Re: Expected test suite behavior”
  1. Michael MontalboMay 25, 2026
  2. Jeff KingMay 25, 2026
  3. Amogh DambalMay 25, 2026
  4. brian m. carlsonMay 25, 2026
  5. Amogh DambalMay 25, 2026
  6. brian m. carlsonMay 26, 2026
  7. Junio C HamanoMay 26, 2026

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.