Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t] i915/gem_pwrite: Enable some subtests for CI
Date: Sun, 08 Nov 2020 22:04:31 -0800	[thread overview]
Message-ID: <874klzgj68.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <20201107134847.65608-1-chris@chris-wilson.co.uk>

On Sat, 07 Nov 2020 05:48:47 -0800, Chris Wilson wrote:
>
> CI blacklists gem_pwrite !basic subtests, but there are a few in there
> are foundational so include them.

Reviewed-by: Ashutosh Dixit <ashutosh.dixit@intel.com>

> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> ---
>  tests/i915/gem_pwrite.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/tests/i915/gem_pwrite.c b/tests/i915/gem_pwrite.c
> index 7a0864637..492b6035c 100644
> --- a/tests/i915/gem_pwrite.c
> +++ b/tests/i915/gem_pwrite.c
> @@ -510,10 +510,10 @@ igt_main_args("s:", NULL, help_str, opt_handler, NULL)
>		}
>	}
>
> -	igt_subtest("self")
> +	igt_subtest("basic-self")
>		pwrite_self(fd);
>
> -	igt_subtest("exhaustion")
> +	igt_subtest("basic-exhaustion")
>		test_exhaustion(fd);
>
>	for (c = cache; c->level != -1; c++) {
> --
> 2.29.2
>
> _______________________________________________
> igt-dev mailing list
> igt-dev@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/igt-dev
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

      parent reply	other threads:[~2020-11-09  6:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-07 13:48 [igt-dev] [PATCH i-g-t] i915/gem_pwrite: Enable some subtests for CI Chris Wilson
2020-11-07 14:47 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2020-11-07 15:51 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2020-11-09  6:04 ` Dixit, Ashutosh [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=874klzgj68.wl-ashutosh.dixit@intel.com \
    --to=ashutosh.dixit@intel.com \
    --cc=chris@chris-wilson.co.uk \
    --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