All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t] tests/perf/i915_ref_count: Skip on __drm_open_driver failure
Date: Mon, 18 Jul 2022 15:50:41 -0700	[thread overview]
Message-ID: <87y1wqavcu.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <20220718223205.1629532-1-ashutosh.dixit@intel.com>

On Mon, 18 Jul 2022 15:32:05 -0700, Ashutosh Dixit wrote:
>
> Skip early on __drm_open_driver() to generate a consistent failure
> signature for CI (rather than a follow-on igt_assert(is_i915_device(fd))).
>
> Cc: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
> Signed-off-by: Ashutosh Dixit <ashutosh.dixit@intel.com>
> ---
>  tests/i915/perf.c | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/tests/i915/perf.c b/tests/i915/perf.c
> index e641d5d2db7e..5502a3fb4e59 100644
> --- a/tests/i915/perf.c
> +++ b/tests/i915/perf.c
> @@ -4838,6 +4838,7 @@ test_i915_ref_count(void)
>	igt_debug("baseline ref count (drm fd closed) = %u\n", baseline);
>
>	drm_fd = __drm_open_driver(DRIVER_INTEL);
> +	igt_require_intel(drm_fd);

The other option might be to use igt_require_fd() here (or something like
that) which would be closer to the signature CI expects from
drm_open_driver().

At the other place in perf.c __drm_open_driver() is followed by
igt_require_gem() which skips using igt_require_intel() and that's why I
used igt_require_intel() here (instead of other options).

Maybe as long as we are skipping one way or another (and not asserting) it
should be ok?


>	devid = intel_get_drm_devid(drm_fd);
>	sysfs = igt_sysfs_open(drm_fd);
>
> --
> 2.34.1
>

  reply	other threads:[~2022-07-18 22:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-18 22:32 [igt-dev] [PATCH i-g-t] tests/perf/i915_ref_count: Skip on __drm_open_driver failure Ashutosh Dixit
2022-07-18 22:50 ` Dixit, Ashutosh [this message]
2022-07-19  0:38   ` Umesh Nerlige Ramappa
2022-07-18 23:29 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2022-07-19  3:38 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2022-07-19  4:01   ` Dixit, Ashutosh
2022-07-19 15:03     ` Vudum, Lakshminarayana
2022-07-19  5:20 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2022-07-19  9:30 ` [igt-dev] ✓ Fi.CI.IGT: " 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=87y1wqavcu.wl-ashutosh.dixit@intel.com \
    --to=ashutosh.dixit@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.