From: Jani Nikula <jani.nikula@intel.com>
To: Jeevan B <jeevan.b@intel.com>, igt-dev@lists.freedesktop.org
Cc: mohammed.thasleem@intel.com, Jeevan B <jeevan.b@intel.com>
Subject: Re: [PATCH i-g-t v2 1/4] tests/intel/kms_pm_dc: Replace require with proper assertion
Date: Tue, 14 Apr 2026 13:51:31 +0300 [thread overview]
Message-ID: <e650ce83d43adb273031ff62f8722b091d2ff338@intel.com> (raw)
In-Reply-To: <20260414095014.55950-2-jeevan.b@intel.com>
On Tue, 14 Apr 2026, Jeevan B <jeevan.b@intel.com> 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>
> Reviewed-by: Mohammed Thasleem <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 8138933d4..f1380ea69 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);
Might rename these check_ functions to assert_ as a follow-up, because
"check" doesn't say what they actually do.
> }
>
> static void setup_dc3co(data_t *data)
--
Jani Nikula, Intel
next prev parent reply other threads:[~2026-04-14 10:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-14 9:50 [PATCH i-g-t v2 0/4] Enable and Add new tests for DC3CO Jeevan B
2026-04-14 9:50 ` [PATCH i-g-t v2 1/4] tests/intel/kms_pm_dc: Replace require with proper assertion Jeevan B
2026-04-14 10:51 ` Jani Nikula [this message]
2026-04-14 9:50 ` [PATCH i-g-t v2 2/4] tests/intel/kms_pm_dc: Enable DC3CO test for PSR2/PR modes Jeevan B
2026-04-14 9:50 ` [PATCH i-g-t v2 3/4] tests/kms_vrr: Add new test for DC3CO validation with LOBF Jeevan B
2026-04-14 9:50 ` [PATCH i-g-t v2 4/4] tests/intel/kms_pm_dc: Add new test for dc3co framedrop validation Jeevan B
2026-04-14 10:53 ` Jani Nikula
2026-04-14 10:34 ` ✓ i915.CI.BAT: success for Enable and Add new tests for DC3CO (rev3) Patchwork
2026-04-14 11:26 ` ✓ Xe.CI.BAT: " Patchwork
2026-04-14 13:01 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-04-14 17:30 ` ✗ i915.CI.Full: " 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=e650ce83d43adb273031ff62f8722b091d2ff338@intel.com \
--to=jani.nikula@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=jeevan.b@intel.com \
--cc=mohammed.thasleem@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