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 v2 6/7] runner/job_list: use case-insensitive regular expressions
Date: Mon, 30 Oct 2023 10:50:01 +0100	[thread overview]
Message-ID: <20231030095206.108025-7-mauro.chehab@linux.intel.com> (raw)
In-Reply-To: <20231030095206.108025-1-mauro.chehab@linux.intel.com>

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

There are some KMS tests that are case-sensitive. Eventually,
those could be blocklisted with a different case, causing troubles
for CI runs.

As it makes no sense to have the same test name with different
cases, handle regular expressions in a case-insensitive way.

Reviewed-by: Kamil Konieczny <kamil.konieczny@linux.intel.com>
Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
---
 runner/settings.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/runner/settings.c b/runner/settings.c
index 788957948b4f..42d8137f18e9 100644
--- a/runner/settings.c
+++ b/runner/settings.c
@@ -323,7 +323,7 @@ static bool add_regex(struct regex_list *list, char *new)
 	GRegex *regex;
 	GError *error = NULL;
 
-	regex = g_regex_new(new, G_REGEX_OPTIMIZE, 0, &error);
+	regex = g_regex_new(new, G_REGEX_CASELESS | G_REGEX_OPTIMIZE, 0, &error);
 	if (error) {
 		usage(stderr, "Invalid regex '%s': %s", new, error->message);
 		g_error_free(error);
-- 
2.41.0

  parent reply	other threads:[~2023-10-30  9:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-30  9:49 [igt-dev] [PATCH i-g-t v2 0/7] better sync test_list.py with igt_runner Mauro Carvalho Chehab
2023-10-30  9:49 ` [igt-dev] [PATCH i-g-t v2 1/7] runner: Normalize testlist entries that don't list subtests Mauro Carvalho Chehab
2023-10-30  9:49 ` [igt-dev] [PATCH i-g-t v2 2/7] runner/runner_tests: Unit tests for binary-name-only testlist entries Mauro Carvalho Chehab
2023-10-30 12:47   ` Kamil Konieczny
2023-10-30  9:49 ` [igt-dev] [PATCH i-g-t v2 3/7] runner/runner_tests: Fix name of no-subtests in unit tests Mauro Carvalho Chehab
2023-10-30 12:48   ` Kamil Konieczny
2023-10-30  9:49 ` [igt-dev] [PATCH i-g-t v2 4/7] igt_runner: don't require root for dry_run Mauro Carvalho Chehab
2023-10-30  9:50 ` [igt-dev] [PATCH i-g-t v2 5/7] scripts/test_list.py: better handle list of tests Mauro Carvalho Chehab
2023-10-30  9:50 ` Mauro Carvalho Chehab [this message]
2023-10-30  9:50 ` [igt-dev] [PATCH i-g-t v2 7/7] runner/runner_tests: add a test to check case-insensitive match Mauro Carvalho Chehab
2023-10-30 12:38   ` Kamil Konieczny
2023-10-30 17:04 ` [igt-dev] ✓ CI.xeBAT: success for better sync test_list.py with igt_runner (rev2) Patchwork
2023-10-30 17:08 ` [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=20231030095206.108025-7-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