public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Sharma, Swati2" <swati2.sharma@intel.com>
To: "Naladala, Ramanaidu" <Ramanaidu.naladala@intel.com>,
	<igt-dev@lists.freedesktop.org>,
	Karthik B S <karthik.b.s@intel.com>
Subject: Re: [PATCH i-g-t v1 0/2] Skip intel unsupported downscale tests
Date: Fri, 20 Mar 2026 15:10:44 +0530	[thread overview]
Message-ID: <38f6a42e-bfc6-4fc9-ba55-d56ff0807ab6@intel.com> (raw)
In-Reply-To: <c25692c3-6896-462c-b4d1-36f0df20ee94@intel.com>

Hi Ramanaidu,

On 20-03-2026 02:02 pm, Naladala, Ramanaidu wrote:
> ++ Karthik
>
> Hi Swati,
>
> On 3/20/2026 1:11 PM, Sharma, Swati2 wrote:
>> Hi Ramanaidu,
>>
>> On 11-03-2026 01:10 pm, Naladala Ramanaidu wrote:
>>> Some scaling tests are expected to be skipped, but they still 
>>> iterate over
>>> all display modes, which generates excessive logging and eventually 
>>> hits
>>> CI disk‑usage limits. To address this, early skip logic is added 
>>> before the
>>> dynamic tests begin, preventing unnecessary mode iterations and 
>>> reducing CI
>>> load.
>> Why can't we handle this in blocklists? 
>
> The tests are already blocklisted, but they continue to run. To 
> address this limitation, I sent a patch.
>
>  According to Karthik, platform blocklisted tests are only excluded in 
> Grafana queries, not during execution. CI intends to generate 
> per‑platform testlists from the blocklists, but it doesn’t seem to be 
> active yet.
There shouldn't be any blocker to use these blocklists in CI. I have 
requested CI to apply those for NVL, if it works well. Same can be done 
for PTL as a WA until we have platform specific testlists.
>
>>>
>>> Naladala Ramanaidu (2):
>>>    tests/kms_plane_scaling: Skip unsupported scaling scenarios
>>>    HAX patch do not merge
>>>
>>>   tests/intel-ci/i915.fast-feedback.testlist | 216 +++-----------
>>>   tests/intel-ci/xe.fast-feedback.testlist   | 323 
>>> +++------------------
>>>   tests/kms_plane_scaling.c                  |  38 +++
>>>   3 files changed, 128 insertions(+), 449 deletions(-)
>>>

      reply	other threads:[~2026-03-20  9:41 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-11  7:40 [PATCH i-g-t v1 0/2] Skip intel unsupported downscale tests Naladala Ramanaidu
2026-03-11  7:40 ` [PATCH i-g-t v1 1/2] tests/kms_plane_scaling: Skip unsupported scaling scenarios Naladala Ramanaidu
2026-03-11 10:00   ` B, Jeevan
2026-03-11 10:15     ` Naladala, Ramanaidu
2026-03-17  7:38   ` [PATCH i-g-t v2] " Naladala Ramanaidu
2026-03-18  4:29     ` Samala, Pranay
2026-03-18  4:42       ` B, Jeevan
2026-03-11  7:40 ` [PATCH i-g-t v1 2/2] HAX patch do not merge Naladala Ramanaidu
2026-03-11 21:50 ` ✗ i915.CI.BAT: failure for Skip intel unsupported downscale tests Patchwork
2026-03-11 21:57 ` ✗ Xe.CI.BAT: " Patchwork
2026-03-12 15:34 ` ✗ Xe.CI.FULL: " Patchwork
2026-03-17 19:26 ` ✗ Xe.CI.BAT: failure for Skip intel unsupported downscale tests (rev2) Patchwork
2026-03-17 19:44 ` ✗ i915.CI.BAT: " Patchwork
2026-03-19  4:40 ` ✗ Xe.CI.FULL: " Patchwork
2026-03-20  7:41 ` [PATCH i-g-t v1 0/2] Skip intel unsupported downscale tests Sharma, Swati2
2026-03-20  8:32   ` Naladala, Ramanaidu
2026-03-20  9:40     ` Sharma, Swati2 [this message]

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=38f6a42e-bfc6-4fc9-ba55-d56ff0807ab6@intel.com \
    --to=swati2.sharma@intel.com \
    --cc=Ramanaidu.naladala@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=karthik.b.s@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