Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Karthik B S <karthik.b.s@intel.com>
To: Kamil Konieczny <kamil.konieczny@linux.intel.com>,
	Mohammed Thasleem <mohammed.thasleem@intel.com>,
	Swati Sharma <swati2.sharma@intel.com>,
	<igt-dev@lists.freedesktop.org>
Subject: Re: [PATCH i-g-t v2] tests/intel-ci/xe: Block kms_display_modes@mst-extended-mode-negative test
Date: Thu, 20 Mar 2025 19:17:35 +0530	[thread overview]
Message-ID: <385f0c01-8961-4c8d-9213-43e0c82dcb49@intel.com> (raw)
In-Reply-To: <20250320133541.3lkne36aa7zox4cd@kamilkon-desk.igk.intel.com>

Hi Thasleem,

On 3/20/2025 7:05 PM, Kamil Konieczny wrote:
> Hi Mohammed,
> On 2025-03-13 at 17:18:32 +0530, Mohammed Thasleem wrote:
>> This negative test was designed to validate ENOSPC errors with 2k-4k or
>> 4k-4k monitors connected via MST, addressing bandwidth issues in MST
>> configurations.
>>
>> However, it is not applicable to current bandwidths, as DP 1.4 supports
>> 4 × 8.1 Gbps, and DP 2.1 has increased this to 4 × 20 Gbps, offering
>> significantly greater display capabilities.
>>
>> v2: Add blacklist for i915.
>>
> +cc Swati and Karthik
>
>> Signed-off-by: Mohammed Thasleem <mohammed.thasleem@intel.com>
>> ---
>>   tests/intel-ci/blacklist.txt    | 4 ++++
>>   tests/intel-ci/xe.blocklist.txt | 1 +
>>   2 files changed, 5 insertions(+)
>>
>> diff --git a/tests/intel-ci/blacklist.txt b/tests/intel-ci/blacklist.txt
>> index 9917bf46a..507c14d58 100644
>> --- a/tests/intel-ci/blacklist.txt
>> +++ b/tests/intel-ci/blacklist.txt
>> @@ -83,6 +83,10 @@ igt@gem_exec_alignment@pi-shared
>>   ###############################################
>>   igt@kms_frontbuffer_tracking@.*drrs.*
>>   ###############################################
>> +#Test is removed, so block it on CI

Since we've completely removed this subtest, we don't need to block this 
separately. Please discard this patch.

https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/commit/1845b2478892457fab2333930c44288970bbb96a 


Thanks,
Karthik.B.S
> Add space before 'Test':
>
> # Test is removed, so block it on CI
>
>> +###############################################
>> +igt@kms_display_modes@mst-extended-mode-negative
>> +###############################################
>>   # Tends to generate invalid configurations
>>   # using CCS planes or configurations that
>>   # exceed HW capabilities resulting in sporadic
>> diff --git a/tests/intel-ci/xe.blocklist.txt b/tests/intel-ci/xe.blocklist.txt
>> index 80ceba9a5..06506f590 100644
>> --- a/tests/intel-ci/xe.blocklist.txt
>> +++ b/tests/intel-ci/xe.blocklist.txt
>> @@ -92,6 +92,7 @@ igt@kms_sysfs_edid_timing
>>   # KMS: Non-Intel tests
>>   ##################################################################
>>   igt@kms_cursor_legacy@modeset-atomic-cursor-hotspot
> Add new section here, as this one is for Non-Intel tests
>
> Regards,
> Kamil
>
>> +igt@kms_display_modes@mst-extended-mode-negative
>>   ##################################################################
>>   # SR-IOV tests too stressful or time-consuming
>>   # to execute all dynamic subtests at once.
>> -- 
>> 2.43.0
>>

  reply	other threads:[~2025-03-20 13:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-06 12:13 [PATCH i-g-t] tests/intel-ci/xe: Block kms_display_modes@mst-extended-mode-negative test Mohammed Thasleem
2025-03-07  2:45 ` ✓ i915.CI.BAT: success for " Patchwork
2025-03-07  2:49 ` ✓ Xe.CI.BAT: " Patchwork
2025-03-07  5:28 ` ✗ i915.CI.Full: failure " Patchwork
2025-03-07 13:19 ` ✗ Xe.CI.Full: " Patchwork
2025-03-13 11:48 ` [PATCH i-g-t v2] " Mohammed Thasleem
2025-03-20 13:35   ` Kamil Konieczny
2025-03-20 13:47     ` Karthik B S [this message]
2025-03-14 16:26 ` ✗ Xe.CI.Full: failure for tests/intel-ci/xe: Block kms_display_modes@mst-extended-mode-negative test (rev2) 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=385f0c01-8961-4c8d-9213-43e0c82dcb49@intel.com \
    --to=karthik.b.s@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=kamil.konieczny@linux.intel.com \
    --cc=mohammed.thasleem@intel.com \
    --cc=swati2.sharma@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