public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Sharma, Swati2" <swati2.sharma@intel.com>
To: "Peres, Martin" <martin.peres@intel.com>,
	"igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Cc: "Latvala, Petri" <petri.latvala@intel.com>,
	Chris Wilson <chris@chris-wilson.co.uk>
Subject: Re: [igt-dev] [PATCH i-g-t] intel-ci: Add testdisplay test to BAT
Date: Fri, 14 Aug 2020 17:47:29 +0530	[thread overview]
Message-ID: <97118255-3361-c627-f73d-4fdb7b088593@intel.com> (raw)
In-Reply-To: <ed96284ce5f34c5fabead75a6329c6f2@intel.com>



On 13-Aug-20 2:56 PM, Peres, Martin wrote:
> Hi,
> 
> I do not think the added time is bad, but wasn't testdisplay considered
> for eviction as it was not testing anything else but the fact that the
> kernel does not blow up on modeset?

Correct. It's for modeset testing. However, Chris commented saying same 
can be tested with kms_setmode@basic. Should we add this test in 
fast-feedback then?
AON, igt@kms_setmode@basic-clone-single-crtc is present.

> 
> Could it be improved to check that we generate a valid image? This might
> require pipe writeback though, so we shouldn't block on that.
> 
> Also, how slow is it when we have 6 pipes and 6 DP displays connected?
> Wouldn't it be taking a lot of time?
> 
Yes indeed it will take long time.

> Martin
> 
> On 2020-08-13 10:24, Sharma, Swati2 wrote:
>> @martin peres any thoughts?
>>
>> On 10-Aug-20 1:59 PM, Sharma, Swati2 wrote:
>>> BAT results
>>> https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_4858/index.html?testfilter=testdisplay
>>>
>>>
>>> Execution time of few CI m/c.
>>> |fi-tgl-dsi|fi-tgl-u2|fi-tgl-y|fi-ehl-1|fi-icl-u2|fi-icl-y|fi-cml-u2|
>>> |  0.352s  |  0.064s | 0.548s |    4.686s |  5.311s | 0.101s | 1.464s  |
>>>
>>> Execution time depends upon which panel is connected if its edp max it
>>> supports 2 resolutions => less time. For HDMI; having multiple
>>> resolutions its taking more time.
>>>
>>> On 06-Aug-20 4:38 PM, Swati Sharma wrote:
>>>> testdisplay should be added to BAT. testdisplay is considered
>>>> to be the most basic test to test display functionality.
>>>> With this test we will be able to test modesetting.
>>>>
>>>> Signed-off-by: Swati Sharma <swati2.sharma@intel.com>
>>>> Cc: Petri Latvala <petri.latvala@intel.com>
>>>> Cc: Karthik B S <karthik.b.s@intel.com>
>>>> ---
>>>>    tests/intel-ci/fast-feedback.testlist | 1 +
>>>>    1 file changed, 1 insertion(+)
>>>>
>>>> diff --git a/tests/intel-ci/fast-feedback.testlist
>>>> b/tests/intel-ci/fast-feedback.testlist
>>>> index b796b264..b245b7a7 100644
>>>> --- a/tests/intel-ci/fast-feedback.testlist
>>>> +++ b/tests/intel-ci/fast-feedback.testlist
>>>> @@ -149,6 +149,7 @@ igt@vgem_basic@dmabuf-mmap
>>>>    igt@vgem_basic@mmap
>>>>    igt@vgem_basic@second-client
>>>>    igt@vgem_basic@sysfs
>>>> +igt@testdisplay
>>>>    # All tests that do module unloading and reloading are executed last.
>>>>    # They will sometimes reveal issues of earlier tests leaving the
>>>>
>>>
>>
> 

-- 
~Swati Sharma
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  reply	other threads:[~2020-08-14 12:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-06 11:08 [igt-dev] [PATCH i-g-t] intel-ci: Add testdisplay test to BAT Swati Sharma
2020-08-06 11:44 ` [igt-dev] ✓ Fi.CI.BAT: success for intel-ci: Add testdisplay test to BAT (rev2) Patchwork
2020-08-06 14:46 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2020-08-10  8:29 ` [igt-dev] [PATCH i-g-t] intel-ci: Add testdisplay test to BAT Sharma, Swati2
2020-08-13  7:24   ` Sharma, Swati2
2020-08-13  9:26     ` Peres, Martin
2020-08-14 12:17       ` Sharma, Swati2 [this message]
2020-08-13  8:39 ` Chris Wilson
2020-08-13  9:12   ` Petri Latvala

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=97118255-3361-c627-f73d-4fdb7b088593@intel.com \
    --to=swati2.sharma@intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=martin.peres@intel.com \
    --cc=petri.latvala@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