From: Junio C Hamano <gitster@pobox.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: Elia Pinto <gitter.spiros@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH v2 1/1] Makefile: add a prerequisite to the coverage-report target
Date: Tue, 12 Apr 2022 09:02:56 -0700 [thread overview]
Message-ID: <xmqqh76ycmrz.fsf@gitster.g> (raw)
In-Reply-To: <220412.8635iiivgm.gmgdl@evledraar.gmail.com> ("Ævar Arnfjörð Bjarmason"'s message of "Tue, 12 Apr 2022 09:51:35 +0200")
Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:
> But that's not what I'm talking about here, I'm just saying that we'd do
> a normal "make test" where we write the gcov tests per-test into
> t/test-results/t0001 and join them at the end of the run.
OK, instead of per directory .gcov, we allow separate recording area
per test, ...
> No, on a multi-core machine the inability to run with -jN is the main
> factor in making this run slow. E.g. on my 8 core box the tests run in
> 2-3 minutes with -j8, with -j1 it's 20-25 minutes.
... and that would make it easier to run the same binary from
different tests in parallel, which makes sense.
I missed that you were talking about running tests in parallel when
you brought up the "running tests can be made cheaper".
> So I'm wondering if the desire to keep the old coverage report around is
> synonymous with the current implementation running so slowly.
Possibly.
next prev parent reply other threads:[~2022-04-12 16:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-09 4:30 [PATCH v2 1/1] Makefile: add a prerequisite to the coverage-report target Elia Pinto
2022-04-11 18:29 ` Junio C Hamano
2022-04-11 21:27 ` Ævar Arnfjörð Bjarmason
2022-04-11 22:59 ` Junio C Hamano
2022-04-12 7:51 ` Ævar Arnfjörð Bjarmason
2022-04-12 16:02 ` Junio C Hamano [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-04-08 20:10 [PATCH] " Junio C Hamano
2022-04-09 3:51 ` [PATCH v2 1/1] " Elia Pinto
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=xmqqh76ycmrz.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=avarab@gmail.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).