From: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: ✗ Fi.CI.BAT: failure for drm/i915: CTS fixes (rev3)
Date: Tue, 25 Jun 2019 16:19:15 +0300 [thread overview]
Message-ID: <5fb0a3c2-ed0d-ba9f-af62-3d3eaedbdbd3@intel.com> (raw)
In-Reply-To: <156146858068.2637.9048284428560004371@skylake-alporthouse-com>
On 25/06/2019 16:16, Chris Wilson wrote:
> Quoting Lionel Landwerlin (2019-06-25 14:09:57)
>> I'm not quite sure what can be tested with those (unless you can
>> exercise the 3d pipeline in this case).
> Sure, it's just setting up the GPU with a full 3D state after all ;)
>
> Making sure that CI does include a functional test for these would be
> useful. I thought we have piglit on icl (or maybe we don't have enough
> icl for that yet?), but do we need crucible as well?
> -Chris
>
There is one piglit test that catches this and quite a few Vulkan CTS tests.
I don't think we have anything in crucible.
Probably not run in CI yet.
-Lionel
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2019-06-25 13:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-25 10:58 [PATCH v3 0/2] drm/i915: CTS fixes Lionel Landwerlin
2019-06-25 10:58 ` [PATCH v3 1/2] drm/i915: whitelist PS_(DEPTH|INVOCATION)_COUNT Lionel Landwerlin
2019-06-25 10:58 ` [PATCH v3 2/2] drm/i915/icl: " Lionel Landwerlin
2019-06-25 12:15 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: CTS fixes (rev3) Patchwork
2019-06-25 12:57 ` ✗ Fi.CI.BAT: failure " Patchwork
2019-06-25 13:09 ` Lionel Landwerlin
2019-06-25 13:14 ` Chris Wilson
2019-06-25 13:24 ` Lionel Landwerlin
2019-06-25 13:28 ` Chris Wilson
2019-06-25 13:16 ` Chris Wilson
2019-06-25 13:19 ` Lionel Landwerlin [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=5fb0a3c2-ed0d-ba9f-af62-3d3eaedbdbd3@intel.com \
--to=lionel.g.landwerlin@intel.com \
--cc=chris@chris-wilson.co.uk \
--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