From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-134636-listarch-gdb-patches=sources.redhat.com@sourceware.org>
Received: (qmail 97296 invoked by alias); 8 Nov 2016 18:34:28 -0000
Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-patches.sourceware.org>
List-Subscribe: <mailto:gdb-patches-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-patches/>
List-Post: <mailto:gdb-patches@sourceware.org>
List-Help: <mailto:gdb-patches-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-patches-owner@sourceware.org
Received: (qmail 97283 invoked by uid 89); 8 Nov 2016 18:34:27 -0000
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-1.7 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,RCVD_IN_SORBS_SPAM,SPF_PASS autolearn=ham version=3.3.2 spammy=barometer, checkout
X-HELO: mail-it0-f51.google.com
Received: from mail-it0-f51.google.com (HELO mail-it0-f51.google.com) (209.85.214.51) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 08 Nov 2016 18:34:26 +0000
Received: by mail-it0-f51.google.com with SMTP id u205so225152173itc.0        for <gdb-patches@sourceware.org>; Tue, 08 Nov 2016 10:34:26 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;        d=1e100.net; s=20130820;        h=x-gm-message-state:mime-version:in-reply-to:references:from:date         :message-id:subject:to:cc;        bh=7RSdjav2JJLtRNcNK1+j0rYj9+5Fc6j7Nb9KPu8J0cU=;        b=CwemONULiQTMl1OvSYw4FI/PamjDJKBGY6F+t2ef4S4gAyXGON2zM+h82PjWA48WjU         XVf2RaPGb+si8pCVC/9xKhqawJxFGlkfBUJoD0bHXX08U5iUzsd7bB2t/9JvVlhTAUI/         4VMUNOXZnt//w3Agss3N4fDHVYpLEAaytvPMveHo080kt+XiT60fI1wE0b1QSBTtrB1x         sxtw9DjK2I36T9kLS06I6YXfXxvED7shlYx/mbH916F7udW4WyYvGklHQ4p8iitSFBMt         LihmkUoJMjNSdGFx0su/VGEDeEzs31o1MzdIebbw8Eqnhlk6q1fp6hqKjZQoqfuK+LAP         gqAw==
X-Gm-Message-State: ABUngveP88VWuMQYN1cViogx4j2bdo/NCrXuXF6Pd4yidnRMomS1KQiXQo16xJM3zC8uKBH0qiu62sWeNijSdA==
X-Received: by 10.107.12.28 with SMTP id w28mr16341438ioi.196.1478630064866; Tue, 08 Nov 2016 10:34:24 -0800 (PST)
MIME-Version: 1.0
Received: by 10.36.159.65 with HTTP; Tue, 8 Nov 2016 10:34:24 -0800 (PST)
In-Reply-To: <CAH=s-PPB7pb1ZFj2GZXeqMsW+H74UQduqeDkSZsS2i+YLd48iA@mail.gmail.com>
References: <CAH=s-PPB7pb1ZFj2GZXeqMsW+H74UQduqeDkSZsS2i+YLd48iA@mail.gmail.com>
From: Matt Rice <ratmice@gmail.com>
Date: Tue, 08 Nov 2016 18:34:00 -0000
Message-ID: <CACTLOFrhJVnyV7i=x2=M+2+wLoLn4OPysdvgY6U7UVRb8TTE+A@mail.gmail.com>
Subject: Re: GDB test coverage
To: Yao Qi <qiyaoltc@gmail.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Content-Type: text/plain; charset=UTF-8
X-IsSubscribed: yes
X-SW-Source: 2016-11/txt/msg00176.txt.bz2

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...