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 3/3] [RFC] scripts/test_list.py: enforce mandatory fields to be filled
Date: Thu, 10 Aug 2023 14:32:31 +0200	[thread overview]
Message-ID: <20230810123402.969597-4-mauro.chehab@linux.intel.com> (raw)
In-Reply-To: <20230810123402.969597-1-mauro.chehab@linux.intel.com>

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

If they won't be filled, compilation will break.

Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
---
 scripts/test_list.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/scripts/test_list.py b/scripts/test_list.py
index c23d6d735edf..d52cf23a18ad 100755
--- a/scripts/test_list.py
+++ b/scripts/test_list.py
@@ -1000,7 +1000,7 @@ class TestList:
         if run_missing:
             for test_name in run_missing:
                 print(f'Warning: Missing documentation for {test_name}')
-        if doc_uneeded or run_missing:
+        if doc_uneeded or run_missing or missing_mandatory_fields:
             sys.exit(1)
 
     #
-- 
2.41.0

  parent reply	other threads:[~2023-08-10 12:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-10 12:32 [igt-dev] [PATCH i-g-t 0/3] Validate Xe field descriptions at build time Mauro Carvalho Chehab
2023-08-10 12:32 ` [igt-dev] [PATCH i-g-t 1/3] xe_test_config.json: mark some fields are mandatory at subtest level Mauro Carvalho Chehab
2023-08-10 12:32 ` [igt-dev] [PATCH i-g-t 2/3] scripts/test_list.py: add a check for missing features Mauro Carvalho Chehab
2023-08-10 12:32 ` Mauro Carvalho Chehab [this message]
2023-08-10 14:45 ` [igt-dev] ✗ Fi.CI.BUILD: failure for Validate Xe field descriptions at build time 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=20230810123402.969597-4-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