All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mauro.chehab@linux.intel.com>
To: igt-dev@lists.freedesktop.org, Petri Latvala <petri.latvala@intel.com>
Cc: Ch Sai Gowtham <sai.gowtham.ch@intel.com>,
	Andrzej Hajda <andrzej.hajda@intel.com>
Subject: [igt-dev] [PATCH v3 08/12] scripts/code_cov_parse_info: better handle test name
Date: Thu, 14 Apr 2022 14:24:58 +0200	[thread overview]
Message-ID: <f2596791b00254a633ca661c6680971c4fa75059.1649939026.git.mchehab@kernel.org> (raw)
In-Reply-To: <cover.1649939026.git.mchehab@kernel.org>

From: Mauro Carvalho Chehab <mchehab@kernel.org>

The TN field generated by standard lcov is weird: it keeps
repeating the TN field from time to time. At genhtml, it seems
that only the first one is used.

As we're using TN to indicate the test name, preserve all different
test names at the output file.

Also, printing such names doesn't really makes sense when
--print-used and --print-unused command line options are used,
and printing a list of 100+ names won't make much sense.

So, just remove printing the test names.

Reviewed-by: Ch Sai Gowtham <sai.gowtham.ch@intel.com>
Reviewed-by: Andrzej Hajda <andrzej.hajda@intel.com>
Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
---

To avoid mailbombing on a large number of people, only mailing lists were C/C on the cover.
See [PATCH v3 00/12] at: https://lore.kernel.org/all/cover.1649939026.git.mchehab@kernel.org/

 scripts/code_cov_parse_info | 20 ++++++++------------
 1 file changed, 8 insertions(+), 12 deletions(-)

diff --git a/scripts/code_cov_parse_info b/scripts/code_cov_parse_info
index 604812b41580..3e1525a67d99 100755
--- a/scripts/code_cov_parse_info
+++ b/scripts/code_cov_parse_info
@@ -17,8 +17,8 @@ my %used_source;
 my %record;
 my %files;
 my @func_regexes;
+my %test_names;
 my @src_regexes;
-my $testname = "";
 
 my $verbose = 0;
 my $ignore_unused = 0;
@@ -99,11 +99,7 @@ sub parse_info_data($)
 		if (m/^TN:(.*)/) {
 			if ($1 ne $cur_test) {
 				$cur_test = $1;
-				if (!$testname) {
-					$testname = $cur_test;
-				} else {
-					$testname = "Code_coverage_tests";
-				}
+				$test_names{$cur_test} = 1;
 			}
 			$source = $before_sf;
 			$func = $before_sf;
@@ -297,9 +293,13 @@ sub write_filtered_file($)
 {
 	my $filter = shift;
 
+	my $filtered = "";
+
+	foreach my $testname(sort keys %test_names) {
+		$filtered .= "TN:$testname\n";
+	}
+
 	# Generates filtered data
-	my $filtered = "TN:$testname\n";
-
 	foreach my $source(sort keys %record) {
 		next if (!$used_source{$source});
 
@@ -363,10 +363,6 @@ sub print_code_coverage($$$)
 
 	return if (!$print_used && !$print_unused);
 
-	if ($testname ne "") {
-		$testname =~ s/(.*)_on_(\w+)$/$1 on $2/;
-		print "TEST: $testname\n";
-	}
 	my $prev_file = "";
 
 	foreach my $func (sort keys(%all_func)) {
-- 
2.35.1

  parent reply	other threads:[~2022-04-14 12:25 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-14 12:24 [igt-dev] [PATCH v3 00/12] code coverage: some improvements Mauro Carvalho Chehab
2022-04-14 12:24 ` [igt-dev] [PATCH v3 01/12] scripts/code_cov*: remove the extensions from them Mauro Carvalho Chehab
2022-04-14 12:24 ` [igt-dev] [PATCH v3 02/12] scripts/code_cov_parse_info: add a tool to parse code coverage info files Mauro Carvalho Chehab
2022-04-14 12:24 ` [igt-dev] [PATCH v3 03/12] scripts/code_cov_gen_report: add support for filtering " Mauro Carvalho Chehab
2022-04-14 12:24 ` [igt-dev] [PATCH v3 04/12] runner: execute code coverage script also from PATH Mauro Carvalho Chehab
2022-04-14 12:24 ` [igt-dev] [PATCH v3 05/12] scripts/meson.build: install code coverage scripts Mauro Carvalho Chehab
2022-04-14 12:24 ` [igt-dev] [PATCH v3 06/12] scripts/code_cov_selftest.sh: test if IGT code coverage is working Mauro Carvalho Chehab
2022-04-14 12:24 ` [igt-dev] [PATCH v3 07/12] docs/code_coverage.md: document the code coverage filter script Mauro Carvalho Chehab
2022-04-14 12:24 ` Mauro Carvalho Chehab [this message]
2022-04-14 12:24 ` [igt-dev] [PATCH v3 09/12] code_cov_parse_info: fix error handling when opening files Mauro Carvalho Chehab
2022-04-14 12:25 ` [igt-dev] [PATCH v3 10/12] code_cov_parse_info: fix --show-lines logic Mauro Carvalho Chehab
2022-04-14 12:25 ` [igt-dev] [PATCH v3 11/12] code_cov_parse_info: add support for exclude filters Mauro Carvalho Chehab
2022-04-14 12:25 ` [igt-dev] [PATCH v3 12/12] code_cov_parse_info: add support for generating html reports Mauro Carvalho Chehab
2022-04-14 12:59 ` [igt-dev] ✗ GitLab.Pipeline: warning for code coverage: some improvements (rev4) Patchwork
2022-04-14 13:17 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2022-04-14 15:12 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2022-04-14 15:49   ` Petri Latvala

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=f2596791b00254a633ca661c6680971c4fa75059.1649939026.git.mchehab@kernel.org \
    --to=mauro.chehab@linux.intel.com \
    --cc=andrzej.hajda@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=petri.latvala@intel.com \
    --cc=sai.gowtham.ch@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.