From: Junio C Hamano <gitster@pobox.com>
To: Elia Pinto <gitter.spiros@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v3] Makefile: add a prerequisite to the coverage-report target
Date: Wed, 13 Apr 2022 22:16:10 -0700 [thread overview]
Message-ID: <xmqqlew82qjp.fsf@gitster.g> (raw)
In-Reply-To: <20220414022513.31465-1-gitter.spiros@gmail.com> (Elia Pinto's message of "Thu, 14 Apr 2022 02:25:13 +0000")
Elia Pinto <gitter.spiros@gmail.com> writes:
> @@ -3421,13 +3422,18 @@ coverage-compile:
> coverage-test: coverage-clean-results coverage-compile
> $(MAKE) CFLAGS="$(COVERAGE_CFLAGS)" LDFLAGS="$(COVERAGE_LDFLAGS)" \
> DEFAULT_TEST_TARGET=test -j1 test
> + touch coverage-test.made
> +
> +coverage-test.made:
> + @make coverage-test
> + touch coverage-test.made
As this target runs "$(MAKE) coverage-test", at the end of which the
.made file is touched anyway, I wonder if we need the second line
here.
I just tried to run this sequence:
$ make distclean
$ make coverage-report
$ make coverage-report
$ make coverage-test
without the "touch" in the recipe for the coverage-test.made target,
and it behaved as I expected them to, i.e.
* got an pristine tree
* built, ran tests and showed report
* showed report without building or running testing
* cleared the gcov files, ran tests and showed report
So, perhaps this patch on top?
Thanks.
Makefile | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git i/Makefile w/Makefile
index fa8cc86276..72ae7fa886 100644
--- i/Makefile
+++ w/Makefile
@@ -3416,8 +3416,7 @@ coverage-test: coverage-clean-results coverage-compile
touch coverage-test.made
coverage-test.made:
- @make coverage-test
- touch coverage-test.made
+ $(MAKE) coverage-test
coverage-prove: coverage-clean-results coverage-compile
$(MAKE) CFLAGS="$(COVERAGE_CFLAGS)" LDFLAGS="$(COVERAGE_LDFLAGS)" \
prev parent reply other threads:[~2022-04-14 5:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-14 2:25 [PATCH v3] Makefile: add a prerequisite to the coverage-report target Elia Pinto
2022-04-14 5:06 ` Junio C Hamano
2022-04-14 5:16 ` Junio C Hamano [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=xmqqlew82qjp.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=gitter.spiros@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).