From: Andrzej Hajda <andrzej.hajda@intel.com>
To: Mauro Carvalho Chehab <mauro.chehab@linux.intel.com>,
igt-dev@lists.freedesktop.org,
Petri Latvala <petri.latvala@intel.com>,
Ch Sai Gowtham <sai.gowtham.ch@intel.com>
Subject: Re: [igt-dev] [PATCH v2 08/12] scripts/code_cov_parse_info: better handle test name
Date: Wed, 13 Apr 2022 15:15:35 +0200 [thread overview]
Message-ID: <39e0c112-26a3-d19b-ddcf-46bbaeaf9cdb@intel.com> (raw)
In-Reply-To: <30f142d1224167426fd006503a977c06d91e1ad3.1649753814.git.mchehab@kernel.org>
On 12.04.2022 10:59, Mauro Carvalho Chehab wrote:
> 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>
> Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
> ---
>
>
Reviewed-by: Andrzej Hajda <andrzej.hajda@intel.com>
Regards
Andrzej
next prev parent reply other threads:[~2022-04-13 13:15 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-12 8:58 [igt-dev] [PATCH v2 00/12] code coverage: some improvements Mauro Carvalho Chehab
2022-04-12 8:59 ` [igt-dev] [PATCH v2 01/12] scripts/code_cov*: remove the extensions from them Mauro Carvalho Chehab
2022-04-12 8:59 ` [igt-dev] [PATCH v2 02/12] scripts/code_cov_parse_info: add a tool to parse code coverage info files Mauro Carvalho Chehab
2022-04-12 8:59 ` [igt-dev] [PATCH v2 03/12] scripts/code_cov_gen_report: add support for filtering " Mauro Carvalho Chehab
2022-04-12 8:59 ` [igt-dev] [PATCH v2 04/12] runner: execute code coverage script also from PATH Mauro Carvalho Chehab
2022-04-12 8:59 ` [igt-dev] [PATCH v2 05/12] scripts/meson.build: install code coverage scripts Mauro Carvalho Chehab
2022-04-12 8:59 ` [igt-dev] [PATCH v2 06/12] scripts/code_cov_selftest.sh: test if IGT code coverage is working Mauro Carvalho Chehab
2022-04-12 8:59 ` [igt-dev] [PATCH v2 07/12] docs/code_coverage.md: document the code coverage filter script Mauro Carvalho Chehab
2022-04-13 13:14 ` Andrzej Hajda
2022-04-12 8:59 ` [igt-dev] [PATCH v2 08/12] scripts/code_cov_parse_info: better handle test name Mauro Carvalho Chehab
2022-04-13 13:15 ` Andrzej Hajda [this message]
2022-04-12 8:59 ` [igt-dev] [PATCH v2 09/12] code_cov_parse_info: fix error handling when opening files Mauro Carvalho Chehab
2022-04-13 13:27 ` Andrzej Hajda
2022-04-14 5:48 ` Mauro Carvalho Chehab
2022-04-12 8:59 ` [igt-dev] [PATCH v2 10/12] code_cov_parse_info: fix --show-lines logic Mauro Carvalho Chehab
2022-04-12 8:59 ` [igt-dev] [PATCH v2 11/12] code_cov_parse_info: add support for exclude filters Mauro Carvalho Chehab
2022-04-13 13:53 ` Andrzej Hajda
2022-04-14 7:03 ` Mauro Carvalho Chehab
2022-04-12 8:59 ` [igt-dev] [PATCH v2 12/12] code_cov_parse_info: add support for generating html reports Mauro Carvalho Chehab
2022-04-13 13:59 ` Andrzej Hajda
2022-04-12 9:40 ` [igt-dev] ✗ GitLab.Pipeline: warning for code coverage: some improvements (rev2) Patchwork
2022-04-12 10:04 ` [igt-dev] ✗ Fi.CI.BAT: failure " Patchwork
2022-04-14 7:28 ` [igt-dev] ✗ Fi.CI.BUILD: failure for code coverage: some improvements (rev3) Patchwork
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=39e0c112-26a3-d19b-ddcf-46bbaeaf9cdb@intel.com \
--to=andrzej.hajda@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=mauro.chehab@linux.intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox