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 1/2] xe_test_config.json: mark some fields are mandatory at subtest level
Date: Thu, 10 Aug 2023 17:10:30 +0200	[thread overview]
Message-ID: <20230810151303.1338975-2-mauro.chehab@linux.intel.com> (raw)
In-Reply-To: <20230810151303.1338975-1-mauro.chehab@linux.intel.com>

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

Some IGT Xe tests were added without proper documentation.
Currently, igt_doc.py doesn't know what fields are mandatory or
not, so it can't enforce it.

Add a field to mark those.

Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
---
 tests/xe/xe_test_config.json | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/tests/xe/xe_test_config.json b/tests/xe/xe_test_config.json
index 08c39de74384..8fb65d02d840 100644
--- a/tests/xe/xe_test_config.json
+++ b/tests/xe/xe_test_config.json
@@ -5,6 +5,7 @@
     "fields": {
         "Category": {
             "_properties_": {
+                "mandatory": true,
                 "description": "Contains the major group for the tested functionality, being hardware, software or firmware"
             },
             "Mega feature": {
@@ -13,10 +14,12 @@
                 },
                 "Sub-category": {
                     "_properties_": {
+                        "mandatory": true,
                         "description": "Contains the the technical feature/functionality"
                     },
                     "Functionality": {
                         "_properties_": {
+                            "mandatory": true,
                             "description": "Groups page table tests on buckets containg more detailed functionality"
                         },
                         "Feature": {
@@ -27,6 +30,7 @@
                     },
                     "Run type": {
                         "_properties_": {
+                            "mandatory": true,
                             "description": "Defines what category of testlist it belongs",
                             "order": [
                                 "boot",
@@ -75,6 +79,7 @@
         },
         "Description" : {
             "_properties_": {
+                "mandatory": true,
                 "description": "Provides a description for the test/subtest."
             }
         }
-- 
2.41.0

  reply	other threads:[~2023-08-10 15:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-10 15:10 [igt-dev] [PATCH i-g-t v2 0/2] Validate Xe field descriptions at build time Mauro Carvalho Chehab
2023-08-10 15:10 ` Mauro Carvalho Chehab [this message]
2023-08-10 19:06   ` [igt-dev] [PATCH i-g-t v2 1/2] xe_test_config.json: mark some fields are mandatory at subtest level Kamil Konieczny
2023-08-10 15:10 ` [igt-dev] [PATCH i-g-t v2 2/2] scripts/test_list.py: add a check for missing features Mauro Carvalho Chehab
2023-08-10 19:07   ` Kamil Konieczny
2023-08-10 16:42 ` [igt-dev] ✗ Fi.CI.BAT: failure for Validate Xe field descriptions at build time (rev2) Patchwork
2023-08-10 19:09   ` Kamil Konieczny
2023-08-11  9:24     ` Yedireswarapu, SaiX Nandan
2023-08-10 17:45 ` [igt-dev] ○ CI.xeBAT: info " Patchwork
2023-08-11  7:20 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2023-08-12  8:46 ` [igt-dev] ✗ Fi.CI.IGT: 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=20230810151303.1338975-2-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