From: Mauro Carvalho Chehab <mauro.chehab@linux.intel.com>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] [PATCH i-g-t 0/3] Produce per-GPU testlists for IntelCI
Date: Wed, 29 Nov 2023 13:25:33 +0100 [thread overview]
Message-ID: <20231129123221.98948-1-mauro.chehab@linux.intel.com> (raw)
From: Mauro Carvalho Chehab <mchehab@kernel.org>
This series contain an improvement to IGT documentation tool to
help generating per-GPU testlists.
This helps producing testlists to be used by Intel CI automation,
as tests that are specific to certain GPUs or ones that won't be
running on some specific configurations can be excluded from
the testlists, making the test results more reliable, saving
execution time on CI and keeping such exclusions properly
documented.
With such change, assuming that some tests would be needed to
be blocked on a "foo" configutation, running
./scripts/igt_doc.py --config tests/intel/xe_test_config.json --intelci-testlist intel-ci
will produce a set of testlist files like:
intel-ci/
└── xe
├── default
│ ├── bat.testlist
│ ├── full.testlist
│ └── other.testlist
└── foo
├── bat.testlist
├── full.testlist
└── other.testlist
Where the "foo" testlists will have a different set of sets on
their testlists, due to blocklisted tests.
Mauro Carvalho Chehab (3):
igt_doc: Add driver name list at JSON configuration
tests/intel: *.json: specify what drivers use such tests
scripts/igt_doc.py: add a logic to generate Intel CI testlists
scripts/igt_doc.py | 192 +++++++++++++++++++++++++++++-
scripts/test_list.py | 5 +
tests/intel/i915_test_config.json | 1 +
tests/intel/kms_test_config.json | 1 +
tests/intel/xe_test_config.json | 1 +
5 files changed, 198 insertions(+), 2 deletions(-)
--
2.42.0
next reply other threads:[~2023-11-29 12:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-29 12:25 Mauro Carvalho Chehab [this message]
2023-11-29 12:25 ` [igt-dev] [PATCH i-g-t 1/3] igt_doc: Add driver name list at JSON configuration Mauro Carvalho Chehab
2023-11-29 15:39 ` Kamil Konieczny
2023-11-29 12:25 ` [igt-dev] [PATCH i-g-t 2/3] tests/intel: *.json: specify what drivers use such tests Mauro Carvalho Chehab
2023-11-29 15:42 ` Kamil Konieczny
2023-11-29 12:25 ` [igt-dev] [PATCH i-g-t 3/3] scripts/igt_doc.py: add a logic to generate Intel CI testlists Mauro Carvalho Chehab
2023-11-29 15:46 ` Kamil Konieczny
2023-11-29 13:38 ` [igt-dev] ✓ Fi.CI.BAT: success for Produce per-GPU testlists for IntelCI (rev2) Patchwork
2023-11-29 14:47 ` [igt-dev] ✓ CI.xeBAT: " Patchwork
2023-11-29 15:41 ` [igt-dev] [PATCH i-g-t 0/3] Produce per-GPU testlists for IntelCI Kamil Konieczny
2023-11-30 13:44 ` [igt-dev] ✓ Fi.CI.IGT: success for Produce per-GPU testlists for IntelCI (rev2) 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=20231129123221.98948-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