From: Karthik B S <karthik.b.s@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: kamil.konieczny@intel.com, swati2.sharma@intel.com,
jari.tahvanainen@intel.com, Karthik B S <karthik.b.s@intel.com>
Subject: [PATCH i-g-t] scripts/test_list: Do not stop the build process in the case of test documantion problem
Date: Sat, 15 Mar 2025 09:38:05 +0530 [thread overview]
Message-ID: <20250315040805.699431-1-karthik.b.s@intel.com> (raw)
Current approach stops whole build process on a case that there is mistake
on documentation. Let's have entry on logs instead and continue.
Small fix also related multiline data e.g. on Description part.
Signed-off-by: Jari Tahvanainen <jari.tahvanainen@intel.com>
Signed-off-by: Karthik B S <karthik.b.s@intel.com>
---
scripts/test_list.py | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/scripts/test_list.py b/scripts/test_list.py
index 867d28400..93a35ca71 100644
--- a/scripts/test_list.py
+++ b/scripts/test_list.py
@@ -1399,7 +1399,7 @@ class TestList:
# Handle multi-line field contents
if current_field:
- match = re.match(r'\s+(.*)', file_line)
+ match = re.match(r'(.*)', file_line)
if match:
if handle_section == 'test':
dic = self.doc[current_test]
@@ -1408,7 +1408,7 @@ class TestList:
if dic[current_field] != '':
dic[current_field] += " "
- dic[current_field] += match.group(1)
+ dic[current_field] += match.group(1).strip()
continue
# Handle multi-line argument contents
@@ -1427,7 +1427,7 @@ class TestList:
continue
file_line.rstrip(r"\n")
- sys.exit(f"{fname}:{file_ln + 1}: Error: unrecognized line. Need to add field at %s?\n\t==> %s" %
+ printf(f"{fname}:{file_ln + 1}: Error: unrecognized line. Need to add field at %s?\n\t==> %s" %
(config_origin, file_line))
def show_subtests(self, sort_field):
--
2.43.0
next reply other threads:[~2025-03-15 4:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-15 4:08 Karthik B S [this message]
2025-03-15 4:48 ` ✓ Xe.CI.BAT: success for scripts/test_list: Do not stop the build process in the case of test documantion problem Patchwork
2025-03-15 5:07 ` ✓ i915.CI.BAT: " Patchwork
2025-03-15 13:45 ` ✗ i915.CI.Full: failure " Patchwork
2025-03-15 13:50 ` ✗ Xe.CI.Full: " Patchwork
2025-03-17 17:01 ` [PATCH i-g-t] " Kamil Konieczny
2025-03-20 14:03 ` Karthik B S
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=20250315040805.699431-1-karthik.b.s@intel.com \
--to=karthik.b.s@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=jari.tahvanainen@intel.com \
--cc=kamil.konieczny@intel.com \
--cc=swati2.sharma@intel.com \
/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