From: Karthik B S <karthik.b.s@intel.com>
To: Bhanuprakash Modem <bhanuprakash.modem@intel.com>,
<igt-dev@lists.freedesktop.org>
Cc: Jani Nikula <jani.nikula@intel.com>
Subject: Re: [igt-dev] [i-g-t] tests/kms_force_connector_basic: Limit "force-load-detect" test to i915
Date: Fri, 21 Apr 2023 14:38:23 +0530 [thread overview]
Message-ID: <5ed5300e-7423-697f-ca74-7ac4eeedfd10@intel.com> (raw)
In-Reply-To: <20230420063515.1791062-1-bhanuprakash.modem@intel.com>
On 4/20/2023 12:05 PM, Bhanuprakash Modem wrote:
> As load_detect_test is enabled only for i915, limit the IGT test
> igt@kms_force_connector_basic@force-load-detect execution to i915
> only.
>
> Cc: Jani Nikula <jani.nikula@intel.com>
> Signed-off-by: Bhanuprakash Modem <bhanuprakash.modem@intel.com>
Reviewed-by: Karthik B S <karthik.b.s@intel.com>
> ---
> tests/intel-ci/xe-fast-feedback.testlist | 1 -
> tests/kms_force_connector_basic.c | 5 ++++-
> 2 files changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/tests/intel-ci/xe-fast-feedback.testlist b/tests/intel-ci/xe-fast-feedback.testlist
> index 5db27c634..3c9276e49 100644
> --- a/tests/intel-ci/xe-fast-feedback.testlist
> +++ b/tests/intel-ci/xe-fast-feedback.testlist
> @@ -167,6 +167,5 @@ igt@kms_addfb_basic@unused-offsets
> igt@kms_addfb_basic@unused-pitches
> igt@kms_force_connector_basic@force-connector-state
> igt@kms_force_connector_basic@force-edid
> -igt@kms_force_connector_basic@force-load-detect
> igt@kms_force_connector_basic@prune-stale-modes
> igt@kms_prop_blob@basic
> diff --git a/tests/kms_force_connector_basic.c b/tests/kms_force_connector_basic.c
> index 35e8153c8..f1508efba 100644
> --- a/tests/kms_force_connector_basic.c
> +++ b/tests/kms_force_connector_basic.c
> @@ -372,8 +372,11 @@ end:
> }
>
> igt_describe("Test to detect forced load.");
> - igt_subtest("force-load-detect")
> + igt_subtest("force-load-detect") {
> + igt_require_i915(drm_fd);
> +
> force_load_detect(drm_fd, connector, res);
> + }
>
> for (i = 0; i < ARRAY_SIZE(tests); i++) {
> igt_describe_f("%s", tests[i].desc);
prev parent reply other threads:[~2023-04-21 9:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-20 6:35 [igt-dev] [i-g-t] tests/kms_force_connector_basic: Limit "force-load-detect" test to i915 Bhanuprakash Modem
2023-04-20 7:38 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2023-04-20 9:35 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2023-04-21 6:59 ` [igt-dev] [i-g-t] " Jani Nikula
2023-04-21 9:08 ` Karthik B S [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=5ed5300e-7423-697f-ca74-7ac4eeedfd10@intel.com \
--to=karthik.b.s@intel.com \
--cc=bhanuprakash.modem@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=jani.nikula@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