From: Karthik B S <karthik.b.s@intel.com>
To: Kamil Konieczny <kamil.konieczny@linux.intel.com>,
<igt-dev@lists.freedesktop.org>, <pranay.samala@intel.com>
Subject: Re: [PATCH i-g-t] tests/kms_addfb_basic: Split tests into subtest groups
Date: Fri, 14 Mar 2025 15:13:57 +0530 [thread overview]
Message-ID: <17c91321-4885-4649-a8dc-4438b782ae26@intel.com> (raw)
In-Reply-To: <20250312204328.mvo7qdvryx77vp72@kamilkon-desk.igk.intel.com>
Hi Kamil,
On 3/13/2025 2:13 AM, Kamil Konieczny wrote:
> Hi Karthik,
> On 2025-03-12 at 16:00:08 +0530, Karthik B S wrote:
>> 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);
> I looked into those tests and imho this needs a major refactor,
> for example there should not be any igt_assert() in a fixture.
> Generally igt tests works ok for one fixture in begin, last one
> at igt_main() end. When used in-between it becomes more
> complicated to handle cleanup.
Thank you for the review.
I tried out by inducing an error using an igt_assert(0) within the
igt_fixture of a subtest group and verified that the this change handles
the issue by not failing the subtests in other subtest groups. As agreed
offline, will use this as a quick fix to handle failures in the current
design and for the long run will check if there is a way these fb
tests(kms_addfb_basic, kms_getfb) can be redesigned to be more robust.
Thanks,
Karthik.B.S
>
> Regards,
> Kamil
>
>>
>> igt_subtest_group {
>> igt_fixture
>> --
>> 2.43.0
>>
next prev parent reply other threads:[~2025-03-14 9:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-12 10:30 [PATCH i-g-t] tests/kms_addfb_basic: Split tests into subtest groups Karthik B S
2025-03-12 20:43 ` Kamil Konieczny
2025-03-14 9:43 ` Karthik B S [this message]
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=17c91321-4885-4649-a8dc-4438b782ae26@intel.com \
--to=karthik.b.s@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=kamil.konieczny@linux.intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.