Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ashutosh Dixit <ashutosh.dixit@intel.com>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] [PATCH i-g-t] kms_fence_pin_leak: check for availabile fences
Date: Thu,  6 Feb 2020 21:26:52 -0800	[thread overview]
Message-ID: <7278cd464aa928fdefb9b4b89df73d3c52fefc42.1581053156.git.ashutosh.dixit@intel.com> (raw)

Need fences to leak fences.

Signed-off-by: Ashutosh Dixit <ashutosh.dixit@intel.com>
---
 tests/kms_fence_pin_leak.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/tests/kms_fence_pin_leak.c b/tests/kms_fence_pin_leak.c
index 8c9e10a56..1ac65e8a1 100644
--- a/tests/kms_fence_pin_leak.c
+++ b/tests/kms_fence_pin_leak.c
@@ -200,6 +200,7 @@ igt_simple_main
 
 	data.drm_fd = drm_open_driver_master(DRIVER_INTEL);
 	igt_require_gem(data.drm_fd);
+	igt_require(gem_available_fences(data.drm_fd) > 0);
 
 	data.devid = intel_get_drm_devid(data.drm_fd);
 
-- 
2.25.0

_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

             reply	other threads:[~2020-02-07  5:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-07  5:26 Ashutosh Dixit [this message]
2020-02-07  6:04 ` [igt-dev] ✓ Fi.CI.BAT: success for kms_fence_pin_leak: check for availabile fences Patchwork
2020-02-07 13:56 ` [igt-dev] [PATCH i-g-t] " Ramalingam C
2020-02-07 14:08   ` Ville Syrjälä
2020-02-07 14:22     ` Ramalingam C
2020-02-10  6:18 ` [igt-dev] ✗ Fi.CI.IGT: failure for " Patchwork
2020-02-18 15:55 ` [igt-dev] ✓ Fi.CI.BAT: success for kms_fence_pin_leak: check for availabile fences (rev2) Patchwork
2020-02-19 23:02 ` [igt-dev] ✗ Fi.CI.IGT: failure " 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=7278cd464aa928fdefb9b4b89df73d3c52fefc42.1581053156.git.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox