From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 2E710A0542; Tue, 6 Sep 2022 18:43:36 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id BDFA6400D6; Tue, 6 Sep 2022 18:43:35 +0200 (CEST) Received: from mta-64-226.siemens.flowmailer.net (mta-64-226.siemens.flowmailer.net [185.136.64.226]) by mails.dpdk.org (Postfix) with ESMTP id 8BCE440042 for ; Tue, 6 Sep 2022 18:43:34 +0200 (CEST) Received: by mta-64-226.siemens.flowmailer.net with ESMTPSA id 202209061643338b3de27245f3640fec for ; Tue, 06 Sep 2022 18:43:33 +0200 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; s=fm1; d=siemens.com; i=felix.moessbauer@siemens.com; h=Date:From:Subject:To:Message-ID:MIME-Version:Content-Type:Content-Transfer-Encoding:Cc; bh=MpbDpmKtmdwEdw6J4YnJ+12HE+hg8gW9WqheTBDLJ8M=; b=lsMg3mZw2nT/MKEL+N5rG033wxjeLUxZahXNtcnvZzPWLYqQ9n6+vYYREZvhTaHjYa5AQn 8q7aF9YNxPJyg938wDoDgM2w0yuPXeheq0g8TfIDhbRzarkk+8SYZEqZRnGDW9UZXXDamM/6 lM3L4lXETtqRgXqGIuGT5ig4hYVX4=; From: Felix Moessbauer To: dev@dpdk.org Cc: william.lam@bytedance.com, chrisswindle@microsoft.com, aconole@redhat.com, david.marchand@redhat.com, henning.schild@siemens.com, Felix Moessbauer Subject: [RFC PATCH 0/1] Add support for code-coverage analysis Date: Tue, 6 Sep 2022 18:43:08 +0200 Message-Id: <20220906164309.1771502-1-felix.moessbauer@siemens.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Flowmailer-Platform: Siemens Feedback-ID: 519:519-72506:519-21489:flowmailer X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org This patch has been developed as part of the DPDK Userspace Summit Hackathon. It provides a PoC for code-coverage analysis for the DPDK project. To generate the report, a developer simply follows the official meson coverage workflow, described in [1]. In doing so, both an HTML report, as well as an XML version is generated for further processing. In short, the following steps are required: - install gcovr - meson -Db_coverage=true build-cov - meson compile -C build-cov - meson test -C build-cov --suite fast-tests - ninja coverage -C build-cov [1] https://mesonbuild.com/howtox.html#producing-a-coverage-report Best regards, Felix Moessbauer Siemens AG Felix Moessbauer (1): Add basic support for code coverage analysis gcovr.cfg | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 gcovr.cfg -- 2.30.2