public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Thasleem, Mohammed" <mohammed.thasleem@intel.com>
To: Jeevan B <jeevan.b@intel.com>, <igt-dev@lists.freedesktop.org>
Cc: <dibin.moolakadan.subrahmanian@intel.com>
Subject: Re: [PATCH i-g-t 1/4] tests/intel/kms_pm_dc: Replace require with proper assertion
Date: Tue, 7 Apr 2026 14:59:09 +0530	[thread overview]
Message-ID: <d9b00a97-6f43-49e4-8061-31b3d70a1f3e@intel.com> (raw)
In-Reply-To: <20260304043805.572087-2-jeevan.b@intel.com>

[-- Attachment #1: Type: text/plain, Size: 1220 bytes --]


On 04-03-2026 10:08 am, Jeevan B wrote:
> The DC3CO video playback simulation test was incorrectly using require at
> the end to check if DC3CO state was entered. This causes the test to be
> marked as SKIP instead of FAIL when DC3CO doesn't work properly, hiding
> real issues. So changing the call from require to assert.
>
> Fixes: b89efa8048e58 ("tests/i915/i915_pm_dc: Check dc3co count to skip the test")
> Signed-off-by: Jeevan B<jeevan.b@intel.com>

LGTM:

Reviewed-by: Mohammed Thasleem <mohammed.thasleem@intel.com> 
<mailto:mohammed.thasleem@intel.com>

> ---
>   tests/intel/kms_pm_dc.c | 3 +--
>   1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/tests/intel/kms_pm_dc.c b/tests/intel/kms_pm_dc.c
> index 39e94f36b..507b6168d 100644
> --- a/tests/intel/kms_pm_dc.c
> +++ b/tests/intel/kms_pm_dc.c
> @@ -312,8 +312,7 @@ static void check_dc3co_with_videoplayback_like_load(data_t *data)
>   		usleep(delay);
>   	}
>   
> -	igt_require_f(igt_dc_state_wait_entry(data->debugfs_fd, IGT_INTEL_CHECK_DC3CO,
> -					      dc3co_prev_cnt), "dc3co-vpb-simulation not enabled\n");
> +	check_dc_counter(data, IGT_INTEL_CHECK_DC3CO, dc3co_prev_cnt);
>   }
>   
>   static void setup_dc3co(data_t *data)

[-- Attachment #2: Type: text/html, Size: 37315 bytes --]

  reply	other threads:[~2026-04-07  9:29 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-04  4:38 [PATCH i-g-t 0/4] Enable and Add new tests for DC3CO Jeevan B
2026-03-04  4:38 ` [PATCH i-g-t 1/4] tests/intel/kms_pm_dc: Replace require with proper assertion Jeevan B
2026-04-07  9:29   ` Thasleem, Mohammed [this message]
2026-03-04  4:38 ` [PATCH i-g-t 2/4] tests/intel/kms_pm_dc: Enable DC3CO test for PSR2/PR modes Jeevan B
2026-04-09  6:06   ` Thasleem, Mohammed
2026-03-04  4:38 ` [PATCH i-g-t 3/4] tests/kms_vrr: Add new test for DC3CO validation with LOBF Jeevan B
2026-04-09  8:12   ` Thasleem, Mohammed
2026-03-04  4:38 ` [PATCH i-g-t 4/4] tests/intel/kms_pm_dc: Add new test for dc3co framedrop validation Jeevan B
2026-04-09 11:03   ` Thasleem, Mohammed
2026-03-04  7:30 ` ✓ Xe.CI.BAT: success for Enable and Add new tests for DC3CO (rev2) Patchwork
2026-03-04  7:30 ` ✓ i915.CI.BAT: " Patchwork
2026-03-05  5:30 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-03-05  9:52 ` ✗ i915.CI.Full: " Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2026-03-03  9:39 [PATCH i-g-t 0/4] Enable and Add new tests for DC3CO Jeevan B
2026-03-03  9:39 ` [PATCH i-g-t 1/4] tests/intel/kms_pm_dc: Replace require with proper assertion Jeevan B

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=d9b00a97-6f43-49e4-8061-31b3d70a1f3e@intel.com \
    --to=mohammed.thasleem@intel.com \
    --cc=dibin.moolakadan.subrahmanian@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=jeevan.b@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