From: Ariel Otilibili <otilibil@eurecom.fr>
To: dev@dpdk.org
Cc: Thomas Monjalon <thomas@monjalon.net>,
David Marchand <david.marchand@redhat.com>,
Robin Jarry <rjarry@redhat.com>,
Ariel Otilibili <otilibil@eurecom.fr>,
stable@dpdk.org
Subject: [PATCH v2 1/1] buildtools: clear out regex syntax warnings
Date: Fri, 13 Dec 2024 15:40:58 +0100 [thread overview]
Message-ID: <20241213144145.59916-2-otilibil@eurecom.fr> (raw)
In-Reply-To: <20241213144145.59916-1-otilibil@eurecom.fr>
* invalid escape sequences now generate SyntaxWarning
* therefore changed syntax to raw string noration.
Link: https://docs.python.org/3/library/re.html#module-re
Fixes: 0aeaf75df87 ("test: define unit tests suites based on test types")
Fixes: 25065ef1f6c ("test: emit warning for orphaned tests")
Cc: stable@dpdk.org
Signed-off-by: Ariel Otilibili <otilibil@eurecom.fr>
---
buildtools/get-test-suites.py | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/buildtools/get-test-suites.py b/buildtools/get-test-suites.py
index c61f6a273f..fd22d25f36 100644
--- a/buildtools/get-test-suites.py
+++ b/buildtools/get-test-suites.py
@@ -6,10 +6,10 @@
import re
input_list = sys.argv[1:]
-test_def_regex = re.compile("REGISTER_([A-Z]+)_TEST\s*\(\s*([a-z0-9_]+)")
+test_def_regex = re.compile(r"REGISTER_([A-Z]+)_TEST\s*\(\s*([a-z0-9_]+)")
test_suites = {}
# track tests not in any test suite.
-non_suite_regex = re.compile("REGISTER_TEST_COMMAND\s*\(\s*([a-z0-9_]+)")
+non_suite_regex = re.compile(r"REGISTER_TEST_COMMAND\s*\(\s*([a-z0-9_]+)")
non_suite_tests = []
def get_fast_test_params(test_name, ln):
--
2.47.1
next parent reply other threads:[~2024-12-13 14:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241208023022.777275-1-otilibil@eurecom.fr>
[not found] ` <20241213144145.59916-1-otilibil@eurecom.fr>
2024-12-13 14:40 ` Ariel Otilibili [this message]
2024-12-13 16:41 ` Robin Jarry
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=20241213144145.59916-2-otilibil@eurecom.fr \
--to=otilibil@eurecom.fr \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=rjarry@redhat.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
/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;
as well as URLs for NNTP newsgroup(s).