From: "Sharma, Swati2" <swati2.sharma@intel.com>
To: Karthik B S <karthik.b.s@intel.com>,
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: Tue, 25 Mar 2025 13:08:37 +0530 [thread overview]
Message-ID: <a9b7125c-2f9a-494e-a1ae-eaee7ffa472f@intel.com> (raw)
In-Reply-To: <56606e53-9eac-437b-afdf-4d6958f8d896@intel.com>
Hi Karthik,
Patch LGTM
Reviewed-by: Swati Sharma <swati2.sharma@intel.com>
On 20-03-2025 07:39 pm, Karthik B S wrote:
> Hi Kamil,
>
> On 3/20/2025 7:00 PM, Kamil Konieczny wrote:
>> Hi Karthik,
>> On 2025-03-14 at 15:13:57 +0530, Karthik B S wrote:
>>> 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
>> Yes, after a second reading this could be a first step
>> followed by refactoring later, so as this could improve
>> testing a little this is
>>
>> Reviewed-by: Kamil Konieczny <kamil.konieczny@linux.intel.com>
>
> Thank you for the rb. Will merge this and then see how overall test
> can be redesigned for the long run.
>
> Thanks,
> Karthik.B.S
>>
>>>> Regards,
>>>> Kamil
>>>>
>>>>> igt_subtest_group {
>>>>> igt_fixture
>>>>> --
>>>>> 2.43.0
>>>>>
next prev parent reply other threads:[~2025-03-25 7:38 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
2025-03-20 13:30 ` Kamil Konieczny
2025-03-20 14:09 ` Karthik B S
2025-03-25 7:38 ` Sharma, Swati2 [this message]
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=a9b7125c-2f9a-494e-a1ae-eaee7ffa472f@intel.com \
--to=swati2.sharma@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=kamil.konieczny@linux.intel.com \
--cc=karthik.b.s@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox