From: Jeff King <peff@peff•net>
To: Michael Montalbo <mmontalbo@gmail•com>
Cc: amoghdambal1@gmail•com, git@vger•kernel.org
Subject: Re: Expected test suite behavior
Date: Mon, 25 May 2026 03:27:11 -0400 [thread overview]
Message-ID: <20260525072711.GE2737798@coredump.intra.peff.net> (raw)
In-Reply-To: <CAC2QwmKgQW2c6_OhepsB1hzXYHxpX0X4eyQS0dPcxRZLOnCdig@mail.gmail.com>
On Sun, May 24, 2026 at 11:20:54PM -0700, Michael Montalbo wrote:
> 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
next prev parent reply other threads:[~2026-05-25 7:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-25 6:20 Expected test suite behavior Michael Montalbo
2026-05-25 7:27 ` Jeff King [this message]
2026-05-25 22:01 ` Amogh Dambal
2026-05-25 22:18 ` brian m. carlson
2026-05-25 22:25 ` Amogh Dambal
2026-05-26 0:41 ` brian m. carlson
2026-05-26 1:11 ` Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2026-05-25 5:38 Amogh Dambal
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=20260525072711.GE2737798@coredump.intra.peff.net \
--to=peff@peff$(echo .)net \
--cc=amoghdambal1@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=mmontalbo@gmail$(echo .)com \
/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