From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Abdiel Janulgue <abdiel.janulgue@linux.intel.com>,
intel-gfx@lists.freedesktop.org
Cc: Tomi Sarvela <"tomi.p.sarvela "@intel.com>
Subject: Re: [PATCH] i-g-t/tests: Drop gem_seqno_wrap, gem_pin, gem_hangcheck_forcewake
Date: Tue, 10 Oct 2017 14:05:42 +0300 [thread overview]
Message-ID: <1507633542.7677.10.camel@linux.intel.com> (raw)
In-Reply-To: <1507625747-28529-1-git-send-email-abdiel.janulgue@linux.intel.com>
+ Chris and Mika for R-b's as they're the test authors
+ Arek, Tomi for CI blacklist reduction
On Tue, 2017-10-10 at 11:55 +0300, Abdiel Janulgue wrote:
> This improves the GEM tests section of I-G-T to make it more
> suitable for CI testing
>
> Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
> Signed-off-by: Abdiel Janulgue <abdiel.janulgue@linux.intel.com>
For future reference, lets have the tags in chronological order.
(Suggested-by: if any) S-o-b, Cc, Reviewed-by etc...
This checks with the test blacklisting TODO items.
Reviewed-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Arek, Tomi; After this is merged, the the following lines can be
removed from CI blacklist.
igt@gem_pin(@.*)?
igt@gem_seqno_wrap(@.*)?
igt@gem_hangcheck_forcewake(@.*)?
Regards, Joonas
--
Joonas Lahtinen
Open Source Technology Center
Intel Corporation
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-10-10 11:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-10 8:55 [PATCH] i-g-t/tests: Drop gem_seqno_wrap, gem_pin, gem_hangcheck_forcewake Abdiel Janulgue
2017-10-10 11:05 ` Joonas Lahtinen [this message]
2017-10-10 17:12 ` Antonio Argenziano
2017-10-10 20:19 ` Chris Wilson
2017-10-10 21:33 ` Antonio Argenziano
2017-10-12 12:39 ` Petri Latvala
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=1507633542.7677.10.camel@linux.intel.com \
--to=joonas.lahtinen@linux.intel.com \
--cc="tomi.p.sarvela "@intel.com \
--cc=abdiel.janulgue@linux.intel.com \
--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 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.