From: Junio C Hamano <gitster@pobox.com>
To: Derrick Stolee <stolee@gmail.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: Git Test Coverage Report (Tuesday, Sept 25)
Date: Wed, 26 Sep 2018 10:59:27 -0700 [thread overview]
Message-ID: <xmqqtvmckum8.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <4bcd63bf-648d-f3f6-dac8-aabe7ea1e480@gmail.com> (Derrick Stolee's message of "Tue, 25 Sep 2018 14:42:24 -0400")
Derrick Stolee <stolee@gmail.com> writes:
> In an effort to ensure new code is reasonably covered by the test
> suite, we now have contrib/coverage-diff.sh to combine the gcov output
> from 'make coverage-test ; make coverage-report' with the output from
> 'git diff A B' to discover _new_ lines of code that are not covered.
>
> This report takes the output of these results after running on four
> branches:
>
> pu: 80e728fa913dc3a1165b6dec9a7afa6052a86325
>
> jch: 0c10634844314ab89666ed0a1c7d36dde7ac9689
>
> next: 76f2f5c1e34c4dbef1029e2984c2892894c444ce
>
> master: fe8321ec057f9231c26c29b364721568e58040f7
>
> master@{1}: 2d3b1c576c85b7f5db1f418907af00ab88e0c303
>
> I ran the test suite on each of these branches on an Ubuntu Linux VM,
> and I'm missing some dependencies (like apache, svn, and perforce) so
> not all tests are run.
Thanks.
> master@{1}..master:
>
> builtin/remote.c
> 5025425dfff ( Shulhan 2018-09-13 20:18:33 +0700
> 864) return error(_("No such remote: '%s'"), name);
> commit-reach.c
> b67f6b26e35 (Derrick Stolee 2018-09-21 08:05:26 -0700
> 559) continue;
> b67f6b26e35 (Derrick Stolee 2018-09-21 08:05:26 -0700
> 569) from->objects[i].item->flags |= assign_flag;
> b67f6b26e35 (Derrick Stolee 2018-09-21 08:05:26 -0700
> 570) continue;
> b67f6b26e35 (Derrick Stolee 2018-09-21 08:05:26 -0700
> 576) result = 0;
> b67f6b26e35 (Derrick Stolee 2018-09-21 08:05:26 -0700
> 577) goto cleanup;
> cat: compat#mingw.c.gcov: No such file or directory
> ll-merge.c
> d64324cb60e (Torsten Bögershausen 2018-09-12 21:32:02
> +0200 379) marker_size =
> DEFAULT_CONFLICT_MARKER_SIZE;
> remote-curl.c
> c3b9bc94b9b (Elijah Newren 2018-09-05 10:03:07 -0700
> 181) options.filter = xstrdup(value);
As I think the data presented here is very valuable, let me ignore
the findings of this specific run (which will be fixed by individual
authors as/if necessary), and focus on the way the data is presented
(which will affect the ease of consumption by authors of future
commits).
These wrapped blame output lines are harder to view. Can we have
this in plain/text without format=flowed at least?
I personally do not mind a monospaced and non-wrapping website, just
I do not mind visiting travis-ci.org for recent results from time to
time. Others may differ.
There is an error message from "cat" in it, by the way.
> preload-index.c
> ae9af12287b (Nguyễn Thái Ngọc Duy 2018-09-15 19:56:04
> +0200 73) struct progress_data *pd =
> p->progress;
> ae9af12287b (Nguyễn Thái Ngọc Duy 2018-09-15 19:56:04
> +0200 75) pthread_mutex_lock(&pd->mutex);
> ae9af12287b (Nguyễn Thái Ngọc Duy 2018-09-15 19:56:04
> +0200 76) pd->n += last_nr - nr;
> ae9af12287b (Nguyễn Thái Ngọc Duy 2018-09-15 19:56:04
> +0200 77) display_progress(pd->progress, pd->n);
> ae9af12287b (Nguyễn Thái Ngọc Duy 2018-09-15 19:56:04
> +0200 78) pthread_mutex_unlock(&pd->mutex);
> ae9af12287b (Nguyễn Thái Ngọc Duy 2018-09-15 19:56:04
> +0200 79) last_nr = nr;
I wonder how much we can save the effort that is needed to scan the
output if we somehow coalesce these consecutive lines that are
attributed to the same commit.
In any case, thanks for doing this.
next prev parent reply other threads:[~2018-09-26 17:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-25 18:42 Git Test Coverage Report (Tuesday, Sept 25) Derrick Stolee
2018-09-25 21:12 ` Ben Peart
2018-09-26 10:43 ` Derrick Stolee
2018-09-26 10:56 ` Jason Pyeron
2018-09-26 11:03 ` Derrick Stolee
2018-09-26 18:43 ` Thomas Gummerer
2018-09-26 18:54 ` Derrick Stolee
2018-09-27 15:21 ` Ben Peart
2018-09-27 15:28 ` Derrick Stolee
2018-09-27 15:38 ` Ævar Arnfjörð Bjarmason
2018-09-26 17:59 ` Junio C Hamano [this message]
2018-09-26 18:44 ` Derrick Stolee
2018-09-27 15:14 ` Ben Peart
2018-09-27 15:16 ` Derrick Stolee
2018-09-26 18:58 ` Elijah Newren
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqtvmckum8.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=stolee@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).