Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Modem, Bhanuprakash" <bhanuprakash.modem@intel.com>
To: Kamil Konieczny <kamil.konieczny@linux.intel.com>,
	<igt-dev@lists.freedesktop.org>
Subject: Re: [PATCH i-g-t 2/5] tests/fbdev: Add testplan documentation
Date: Wed, 29 May 2024 17:04:07 +0530	[thread overview]
Message-ID: <b0ed31c3-c492-41d5-a88d-4f47c611991c@intel.com> (raw)
In-Reply-To: <20240528153918.sndsnr4k3vn2r526@kamilkon-DESK.igk.intel.com>

Hi Kamil,

On 28-05-2024 09:09 pm, Kamil Konieczny wrote:
> Hi Bhanuprakash,
> On 2024-05-28 at 11:12:20 +0530, Bhanuprakash Modem wrote:
>> Add testplan documentation to fbdev tests.
>>
>> Cc: Kamil Konieczny <kamil.konieczny@linux.intel.com>
>> Signed-off-by: Bhanuprakash Modem <bhanuprakash.modem@intel.com>
>> ---
>>   tests/fbdev.c | 39 +++++++++++++++++++++++++++++++++++++++
>>   1 file changed, 39 insertions(+)
>>
>> diff --git a/tests/fbdev.c b/tests/fbdev.c
>> index 794882a6a..f329e6ac6 100644
>> --- a/tests/fbdev.c
>> +++ b/tests/fbdev.c
>> @@ -21,6 +21,15 @@
>>    * IN THE SOFTWARE.
>>    */
>>   
>> +/**
>> + * TEST: fbdev
>> + * Category: Display
>> + * Description: Sanity test for framebuffer device.
>> + * Driver requirement: i915, xe
> 
> I am not sure we need it? I mean it can run on all gpus,
> not only Intel?

"Driver requirement" is Intel thing to differentiate between i915 & xe 
specific tests (As few kms tests contains both i915 & xe specific 
subtests in same test file).

> 
>> + * Functionality: fbdev
>> + * Mega feature: General Display Features
>> + * Test category: functionality test
> 
> Please sort these fields after other tests, see recent Kasia
> patchseries or look into other kms tests.

These fields are already sorted alphabetically. We are using the same 
style for entire KMS tests.

> 
> Could you also fix this test? After merging locally your
> patchset I got errors from 'meson test -C build':

This issue is not seen in my local/CI:
https://gitlab.freedesktop.org/gfx-ci/igt-ci-tags/-/jobs/59210298

Ok:                 423
Expected Fail:      4
Fail:               0
Unexpected Pass:    0
Skipped:            0
Timeout:            0

> 
> It turns out test uses in igt_main:
> 
> igt_subtest_group {
>      mode_tests(fd);
> }
> 
> and then defines subtests in functions. That is causing test failing.

I guess, that kind of implementation is legal in IGT.

- Bhanu

> 
> Regards,
> Kamil
> 
> 
>> + */
>>   #include "config.h"
>>   
>>   #include "igt.h"
>> @@ -39,6 +48,36 @@
>>   
>>   #include "igt.h"
>>   
>> +/**
>> + * SUBTEST: eof
>> + * Description: Check framebuffer access near EOF
>> + *
>> + * SUBTEST: info
>> + * Description: Check if screeninfo is valid
>> + *
>> + * SUBTEST: nullptr
>> + * Description: Check framebuffer access with NULL
>> + *
>> + * SUBTEST: pan
>> + * Description: Check panning / page flipping
>> + *
>> + * SUBTEST: read
>> + * Description: Check read operations on framebuffer memory
>> + *
>> + * SUBTEST: write
>> + * Description: Check write operations on framebuffer memory
>> + */
>> +
>> +/**
>> + * SUBTEST: unaligned-%s
>> + * Description: Check %arg[1] operations on unaligned locations in framebuffer memory
>> + *
>> + * arg[1]:
>> + *
>> + * @read:	read
>> + * @write:	write
>> + */
>> +
>>   #define PANSTEP(panstep_) \
>>   	((panstep_) ? (panstep_) : 1)
>>   
>> -- 
>> 2.43.2
>>

  reply	other threads:[~2024-05-29 11:34 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-28  5:42 [PATCH i-g-t 0/5] Enable fbdev tests on XE Bhanuprakash Modem
2024-05-28  5:42 ` [PATCH i-g-t 1/5] tests/fbdev: Fix fd closure Bhanuprakash Modem
2024-05-28 15:26   ` Kamil Konieczny
2024-05-28  5:42 ` [PATCH i-g-t 2/5] tests/fbdev: Add testplan documentation Bhanuprakash Modem
2024-05-28 15:39   ` Kamil Konieczny
2024-05-29 11:34     ` Modem, Bhanuprakash [this message]
2024-05-29 15:15       ` Kamil Konieczny
2024-05-28  5:42 ` [PATCH i-g-t 3/5] tests/intel/kms_test_config: Add fbdev tests to testplan Bhanuprakash Modem
2024-05-29 14:59   ` Kamil Konieczny
2024-05-28  5:42 ` [PATCH i-g-t 4/5] tests/intel-ci/xe: Drop fbdev tests from blocklist Bhanuprakash Modem
2024-05-29 15:16   ` Kamil Konieczny
2024-05-28  5:42 ` [PATCH i-g-t 5/5] tests/intel-ci/xe: Add fbdev tests to XE BAT Bhanuprakash Modem
2024-05-29 15:00   ` Kamil Konieczny
2024-06-05  8:23   ` Karthik B S
2024-05-28  6:16 ` ✓ CI.xeBAT: success for Enable fbdev tests on XE Patchwork
2024-05-28  6:24 ` ✗ Fi.CI.BAT: failure " Patchwork
2024-05-28  7:40   ` Modem, Bhanuprakash
2024-05-29  5:28     ` Illipilli, TejasreeX
2024-05-28  7:11 ` ✗ CI.xeFULL: " Patchwork
2024-05-29  5:11 ` ✓ Fi.CI.BAT: success " Patchwork
2024-05-29 23:04 ` ✗ Fi.CI.IGT: failure " 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=b0ed31c3-c492-41d5-a88d-4f47c611991c@intel.com \
    --to=bhanuprakash.modem@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=kamil.konieczny@linux.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