From: Chris Wilson <chris@chris-wilson.co.uk>
To: intel-gfx@lists.freedesktop.org
Cc: igt-dev@lists.freedesktop.org
Subject: [Intel-gfx] [PATCH i-g-t v2] i915/gem_mmap_gtt: Disregard forked subtests on ICL for reasons
Date: Mon, 10 Jun 2019 14:02:00 +0100 [thread overview]
Message-ID: <20190610130200.21164-1-chris@chris-wilson.co.uk> (raw)
In-Reply-To: <20190610125550.20870-1-chris@chris-wilson.co.uk>
Nothing to see here, please move along.
References: https://bugs.freedesktop.org/show_bug.cgi?id=110882
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com>
Cc: Martin Peres <martin.peres@linux.intel.com>
---
tests/i915/gem_mmap_gtt.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/tests/i915/gem_mmap_gtt.c b/tests/i915/gem_mmap_gtt.c
index 034658e64..6f3a9c36e 100644
--- a/tests/i915/gem_mmap_gtt.c
+++ b/tests/i915/gem_mmap_gtt.c
@@ -656,6 +656,9 @@ test_huge_copy(int fd, int huge, int tiling_a, int tiling_b, int ncpus)
uint64_t huge_object_size, i;
unsigned mode = CHECK_RAM;
+ igt_fail_on_f(intel_gen(devid) >= 11 && ncpus > 1,
+ "Please adjust your expectations, https://bugs.freedesktop.org/show_bug.cgi?id=110882\n");
+
switch (huge) {
case -2:
huge_object_size = gem_mappable_aperture_size() / 4;
--
2.20.1
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-06-10 13:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-10 12:55 [igt-dev] [PATCH i-g-t] i915/gem_mmap_gtt: Disregard forked subtests on ICL for reasons Chris Wilson
2019-06-10 12:59 ` Martin Peres
2019-06-10 13:02 ` Chris Wilson [this message]
2019-06-10 14:16 ` [igt-dev] ✓ Fi.CI.BAT: success for i915/gem_mmap_gtt: Disregard forked subtests on ICL for reasons (rev2) Patchwork
2019-06-11 9:53 ` [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=20190610130200.21164-1-chris@chris-wilson.co.uk \
--to=chris@chris-wilson.co.uk \
--cc=igt-dev@lists.freedesktop.org \
--cc=intel-gfx@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