From: Mauro Carvalho Chehab <mauro.chehab@linux.intel.com>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] [PATCH i-g-t v4 00/11] Make test_list.py more generic
Date: Thu, 31 Aug 2023 16:52:02 +0200 [thread overview]
Message-ID: <20230831145509.477543-1-mauro.chehab@linux.intel.com> (raw)
From: Mauro Carvalho Chehab <mchehab@kernel.org>
While most of the code at test_list.py is generic, it contains a
couple of IGT-specific stuff on it.
I'm planning to make it more generic, as we also need to document
in-kernel tests (KUnit).
So, let's remove what's specific to IGT to the main logic. This
way, the same code can be sent to the Linux Kernel upstream,
to be used to document kunit and kselftests there.
---
v4:
- patches reordered;
- removed the patches related to testplan check, as those caused
build problems at the last submissions. Let's merge first the
main changes. I'll submit the last two patches on a separate
PR.
v3:
- fixed dependencies for built_script target;
- added an extra cleanup patch to better handle internal fields.
Mauro Carvalho Chehab (11):
scripts/test_list.py: make the class more generic
scripts/test_list.py: rename the internal summary value
scripts/test_list.py: document what BAT stands for
scripts/test_list.py: close config file before start processing
scripts/test_list.py: filename arguments for print_ methods are
optional
scripts/test_list.py: add a check before deleting properties
scripts/test_list.py: skip some internal fields
scripts/test_list.py: add support to return a string instead of print
scripts/test_list.py: don't rely on file name to parse config
scripts/test_list.py: allow passing a config dict directly
scripts/igt_doc.py: use field names when create a TestList instance
scripts/igt_doc.py | 6 +-
scripts/test_list.py | 377 +++++++++++++++++++++++--------------------
2 files changed, 205 insertions(+), 178 deletions(-)
mode change 100755 => 100644 scripts/test_list.py
--
2.41.0
next reply other threads:[~2023-08-31 14:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-31 14:52 Mauro Carvalho Chehab [this message]
2023-08-31 14:52 ` [igt-dev] [PATCH i-g-t v4 01/11] scripts/test_list.py: make the class more generic Mauro Carvalho Chehab
2023-08-31 14:52 ` [igt-dev] [PATCH i-g-t v4 02/11] scripts/test_list.py: rename the internal summary value Mauro Carvalho Chehab
2023-08-31 14:52 ` [igt-dev] [PATCH i-g-t v4 03/11] scripts/test_list.py: document what BAT stands for Mauro Carvalho Chehab
2023-08-31 14:52 ` [igt-dev] [PATCH i-g-t v4 04/11] scripts/test_list.py: close config file before start processing Mauro Carvalho Chehab
2023-08-31 17:13 ` Kamil Konieczny
2023-08-31 14:52 ` [igt-dev] [PATCH i-g-t v4 05/11] scripts/test_list.py: filename arguments for print_ methods are optional Mauro Carvalho Chehab
2023-08-31 14:52 ` [igt-dev] [PATCH i-g-t v4 06/11] scripts/test_list.py: add a check before deleting properties Mauro Carvalho Chehab
2023-08-31 14:52 ` [igt-dev] [PATCH i-g-t v4 07/11] scripts/test_list.py: skip some internal fields Mauro Carvalho Chehab
2023-08-31 17:16 ` Kamil Konieczny
2023-08-31 14:52 ` [igt-dev] [PATCH i-g-t v4 08/11] scripts/test_list.py: add support to return a string instead of print Mauro Carvalho Chehab
2023-08-31 17:17 ` Kamil Konieczny
2023-08-31 14:52 ` [igt-dev] [PATCH i-g-t v4 09/11] scripts/test_list.py: don't rely on file name to parse config Mauro Carvalho Chehab
2023-08-31 14:52 ` [igt-dev] [PATCH i-g-t v4 10/11] scripts/test_list.py: allow passing a config dict directly Mauro Carvalho Chehab
2023-08-31 14:52 ` [igt-dev] [PATCH i-g-t v4 11/11] scripts/igt_doc.py: use field names when create a TestList instance Mauro Carvalho Chehab
2023-08-31 19:35 ` [igt-dev] ✗ GitLab.Pipeline: warning for Make test_list.py more generic Patchwork
2023-08-31 20:02 ` [igt-dev] ✓ CI.xeBAT: success " Patchwork
2023-08-31 20:12 ` [igt-dev] ✗ Fi.CI.BAT: failure " 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=20230831145509.477543-1-mauro.chehab@linux.intel.com \
--to=mauro.chehab@linux.intel.com \
--cc=igt-dev@lists.freedesktop.org \
/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