From: Karthik B S <karthik.b.s@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: pranay.samala@intel.com, Karthik B S <karthik.b.s@intel.com>
Subject: [PATCH i-g-t] tests/kms_addfb_basic: Split tests into subtest groups
Date: Wed, 12 Mar 2025 16:00:08 +0530 [thread overview]
Message-ID: <20250312103008.613087-1-karthik.b.s@intel.com> (raw)
Multiple subtest groups exist in kms_addfb_basic with individual
igt_fixutre calls. Split these using igt_subtest_group so that any
failure in the fixture of one of the individual subtest groups don't
affect the results of subtests in other groups.
Signed-off-by: Karthik B S <karthik.b.s@intel.com>
---
tests/kms_addfb_basic.c | 15 ++++++++++-----
1 file changed, 10 insertions(+), 5 deletions(-)
diff --git a/tests/kms_addfb_basic.c b/tests/kms_addfb_basic.c
index e5ff9ea32..268e4e0e4 100644
--- a/tests/kms_addfb_basic.c
+++ b/tests/kms_addfb_basic.c
@@ -989,15 +989,20 @@ igt_main
igt_require(has_addfb2_iface(fd));
}
- invalid_tests(fd);
+ igt_subtest_group
+ invalid_tests(fd);
- pitch_tests(fd);
+ igt_subtest_group
+ pitch_tests(fd);
- prop_tests(fd);
+ igt_subtest_group
+ prop_tests(fd);
- master_tests(fd);
+ igt_subtest_group
+ master_tests(fd);
- tiling_tests(fd);
+ igt_subtest_group
+ tiling_tests(fd);
igt_subtest_group {
igt_fixture
--
2.43.0
next reply other threads:[~2025-03-12 10:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-12 10:30 Karthik B S [this message]
2025-03-12 20:43 ` [PATCH i-g-t] tests/kms_addfb_basic: Split tests into subtest groups Kamil Konieczny
2025-03-14 9:43 ` Karthik B S
2025-03-20 13:30 ` Kamil Konieczny
2025-03-20 14:09 ` Karthik B S
2025-03-25 7:38 ` Sharma, Swati2
2025-03-13 2:45 ` ✓ Xe.CI.BAT: success for " Patchwork
2025-03-13 3:01 ` ✓ i915.CI.BAT: " Patchwork
2025-03-13 4:52 ` ✗ i915.CI.Full: failure " Patchwork
2025-03-26 4:37 ` Karthik B S
2025-03-13 17:49 ` ✓ Xe.CI.Full: 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=20250312103008.613087-1-karthik.b.s@intel.com \
--to=karthik.b.s@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=pranay.samala@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