From: Mauro Carvalho Chehab <mauro.chehab@linux.intel.com>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] [PATCH i-g-t 0/7] better sync test_list.py with igt_runner
Date: Tue, 24 Oct 2023 16:11:03 +0200 [thread overview]
Message-ID: <20231024141855.160633-1-mauro.chehab@linux.intel.com> (raw)
From: Mauro Carvalho Chehab <mchehab@kernel.org>
This patch series comes after:
https://patchwork.freedesktop.org/series/125401/
(The three patches from it were added here, to allow CI to test
the new patches)
It contains some additional changes meant to sync how IGT
runner, documentation tools and CI works with regular expressions:
- the IGT runner regular expressions are now case-insensitive.
As there are several KMS tests have upper case letters to indicate
port entries. There's no sense of having tests named:
igt@foo-port-A being different than igt@foo-port-a. One of
the runner tests were changed to only match if case is not
sensitive on regular expressions;
- when igt_runner is in dry-run mode, it doesn't need root
permissions;
- currently, test_list.py is considering testlists as regular
expressions, but they're really a normal list of tests.
Change the logic to handle it accordingly.
Mauro Carvalho Chehab (4):
igt_runner: don't require root for dry_run
scripts/test_list.py: better handle list of tests
runner/job_list: use case-insensitive regular expressions
runner/runner_tests: change a regex to match case-insensitive
Petri Latvala (3):
runner: Normalize testlist entries that don't list subtests
runner/runner_tests: Unit tests for binary-name-only testlist entries
runner/runner_tests: Fix name of no-subtests in unit tests
runner/job_list.c | 22 +++++++++-
runner/runner_tests.c | 74 +++++++++++++++++++++++++++++++-
runner/settings.c | 3 +-
scripts/test_list.py | 54 ++++++++++++++++-------
tests/intel/kms_test_config.json | 2 +-
tests/intel/xe_test_config.json | 1 +
6 files changed, 136 insertions(+), 20 deletions(-)
--
2.41.0
next reply other threads:[~2023-10-24 14:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-24 14:11 Mauro Carvalho Chehab [this message]
2023-10-24 14:11 ` [igt-dev] [PATCH i-g-t 1/7] runner: Normalize testlist entries that don't list subtests Mauro Carvalho Chehab
2023-10-24 14:11 ` [igt-dev] [PATCH i-g-t 2/7] runner/runner_tests: Unit tests for binary-name-only testlist entries Mauro Carvalho Chehab
2023-10-24 14:11 ` [igt-dev] [PATCH i-g-t 3/7] runner/runner_tests: Fix name of no-subtests in unit tests Mauro Carvalho Chehab
2023-10-24 14:11 ` [igt-dev] [PATCH i-g-t 4/7] igt_runner: don't require root for dry_run Mauro Carvalho Chehab
2023-10-25 7:53 ` Kamil Konieczny
2023-10-24 14:11 ` [igt-dev] [PATCH i-g-t 5/7] scripts/test_list.py: better handle list of tests Mauro Carvalho Chehab
2023-10-25 7:54 ` Kamil Konieczny
2023-10-24 14:11 ` [igt-dev] [PATCH i-g-t 6/7] runner/job_list: use case-insensitive regular expressions Mauro Carvalho Chehab
2023-10-25 7:56 ` Kamil Konieczny
2023-10-24 14:11 ` [igt-dev] [PATCH i-g-t 7/7] runner/runner_tests: change a regex to match case-insensitive Mauro Carvalho Chehab
2023-10-25 9:56 ` Kamil Konieczny
2023-10-30 9:56 ` Mauro Carvalho Chehab
2023-10-24 15:45 ` [igt-dev] ✓ Fi.CI.BAT: success for better sync test_list.py with igt_runner Patchwork
2023-10-24 15:46 ` [igt-dev] ✗ GitLab.Pipeline: warning " Patchwork
2023-10-25 4:17 ` [igt-dev] ✗ Fi.CI.IGT: 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=20231024141855.160633-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