Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mauro.chehab@linux.intel.com>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] [PATCH i-g-t] scripts/test_list.py: fix subtest regex match
Date: Mon, 30 Oct 2023 16:43:11 +0100	[thread overview]
Message-ID: <20231030154311.140142-1-mauro.chehab@linux.intel.com> (raw)

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

Fix a regression introduced by:
	6e3e8e6d7c05 ("scripts/test_list.py: better handle list of tests")

After such change, regex will only do full match, but it needs also to
consider subtests, if the syntax is just igt@test.

Fixes: 6e3e8e6d7c05 ("scripts/test_list.py: better handle list of tests")
Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
---
 scripts/test_list.py | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/scripts/test_list.py b/scripts/test_list.py
index 06215242107a..741ec5f4b5b5 100644
--- a/scripts/test_list.py
+++ b/scripts/test_list.py
@@ -476,6 +476,8 @@ class TestList:
                 test = match.group(1)
                 subtest = match.group(2)
                 test_name = f"{test}{subtest}"
+                if not test_name.endswith("$"):
+                    test_name += r"(\@.*)?$"
 
                 if match_type in match_type_regex:
                     testlist[name].append(re.compile(test_name, flags))
-- 
2.41.0

             reply	other threads:[~2023-10-30 15:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-30 15:43 Mauro Carvalho Chehab [this message]
2023-10-30 19:33 ` [igt-dev] ✓ Fi.CI.BAT: success for scripts/test_list.py: fix subtest regex match Patchwork
2023-10-30 20:33 ` [igt-dev] ✗ CI.xeBAT: failure " Patchwork
2023-10-31  8:46 ` [igt-dev] [PATCH i-g-t] " Kamil Konieczny
2023-10-31 19:16 ` [igt-dev] ✗ Fi.CI.IGT: failure for " 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=20231030154311.140142-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