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 0/4] Fix bad documentation validation logic
Date: Mon,  9 Oct 2023 12:01:37 +0200	[thread overview]
Message-ID: <20231009100332.392968-1-mauro.chehab@linux.intel.com> (raw)

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

There's currently a bug at the logic which checks for IGT documentation:
it is not reporting all cases of undocumented tests.

Patch 1 on this series fix it, and uses a simpler logic to check for
differences between documented and existing tests.

After the fix, there will be 6 tests out of sync:

$ ./scripts/igt_doc.py --config tests/intel/xe_*.json --check
Warning: Documented igt@xe_sysfs_scheduler@job_timeout_ms-nonprivileged-user doesn't exist on source files
Warning: Documented igt@xe_sysfs_scheduler@preempt_timeout_us-nonprivileged-user doesn't exist on source files
Warning: Documented igt@xe_sysfs_scheduler@timeslice_duration_us-nonprivileged-user doesn't exist on source files

$ ./scripts/igt_doc.py --config tests/intel/kms_*.json --check
Warning: Documented igt@kms_big_fb@linear-addfb-size-offset-overflow doesn't exist on source files
Warning: Documented igt@kms_big_fb@linear-addfb-size-overflow doesn't exist on source files
Warning: Documented igt@kms_frontbuffer_tracking@fbc-slowdraw doesn't exist on source files

The remaining patches on this series fix them.

Mauro Carvalho Chehab (4):
  scripts/test_list.py: fix and simplify missing doc check
  intel/xe_sysfs_scheduler.c: remove nonpriviledged-user tests
  intel/kms_big_fb.c: remove linear-addfb-size*-overflow docs
  intel/kms_frontbuffer_tracking.c: remove fbc-slowdraw test

 scripts/test_list.py                   | 34 +++-----------------------
 tests/intel/kms_big_fb.c               | 16 ------------
 tests/intel/kms_frontbuffer_tracking.c |  7 ------
 tests/intel/xe_sysfs_scheduler.c       |  4 ---
 4 files changed, 4 insertions(+), 57 deletions(-)

-- 
2.41.0

             reply	other threads:[~2023-10-09 10:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-09 10:01 Mauro Carvalho Chehab [this message]
2023-10-09 10:01 ` [igt-dev] [PATCH i-g-t 1/4] scripts/test_list.py: fix and simplify missing doc check Mauro Carvalho Chehab
2023-10-09 10:46   ` Kamil Konieczny
2023-10-09 10:01 ` [igt-dev] [PATCH i-g-t 2/4] intel/xe_sysfs_scheduler.c: remove nonpriviledged-user tests Mauro Carvalho Chehab
2023-10-09 10:23   ` Kamil Konieczny
2023-10-09 10:01 ` [igt-dev] [PATCH i-g-t 3/4] intel/kms_big_fb.c: remove linear-addfb-size*-overflow docs Mauro Carvalho Chehab
2023-10-09 10:27   ` Kamil Konieczny
2023-10-09 10:01 ` [igt-dev] [PATCH i-g-t 4/4] intel/kms_frontbuffer_tracking.c: remove fbc-slowdraw test Mauro Carvalho Chehab
2023-10-09 10:30   ` Kamil Konieczny
2023-10-09 10:51 ` [igt-dev] ✓ Fi.CI.BAT: success for Fix bad documentation validation logic Patchwork
2023-10-09 11:15 ` [igt-dev] ✓ CI.xeBAT: " Patchwork
2023-10-09 12:45 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2023-10-09 16:17   ` Kamil Konieczny
2023-10-10  9:32     ` Yedireswarapu, SaiX Nandan
2023-10-10  9:23 ` [igt-dev] ✓ Fi.CI.IGT: success " 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=20231009100332.392968-1-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