Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Matt Rice <ratmice@gmail.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: GDB test coverage
Date: Tue, 08 Nov 2016 18:34:00 -0000	[thread overview]
Message-ID: <CACTLOFrhJVnyV7i=x2=M+2+wLoLn4OPysdvgY6U7UVRb8TTE+A@mail.gmail.com> (raw)
In-Reply-To: <CAH=s-PPB7pb1ZFj2GZXeqMsW+H74UQduqeDkSZsS2i+YLd48iA@mail.gmail.com>

On Tue, Nov 8, 2016 at 9:38 AM, Yao Qi <qiyaoltc@gmail.com> wrote:
>
> I am sure we can still get more from these coverage results.  How do we
> make full use of coverage tests?  What I can think of are
>  - we can find some never-used functions, and remove some of them,
>  - add more test cases to address some low-coverage areas,

A while back I would run a per-commit coverage under something like
the build bot, and commit the results to a git repository, (one of the
output formats of gcov does compress fairly well...)

One thing that I noticed was that coverage would swing fairly wildly
(even when running the coverage under the same checkout of a commit
without changes) due to the races in the testsuite.

I'm not sure if that would still be the case or not, this made it
fairly difficult to isolate the particular effect that any given
commit had on the coverage.
which I thought would have made a nice barometer of sorta...


      reply	other threads:[~2016-11-08 18:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-08 17:38 Yao Qi
2016-11-08 18:34 ` Matt Rice [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='CACTLOFrhJVnyV7i=x2=M+2+wLoLn4OPysdvgY6U7UVRb8TTE+A@mail.gmail.com' \
    --to=ratmice@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=qiyaoltc@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