Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mauro.chehab@linux.intel.com>
To: Bhanuprakash Modem <bhanuprakash.modem@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [V3 i-g-t 3/4] testplan/i915: Exclude non-i915 tests from i915 testplan
Date: Tue, 4 Jul 2023 09:16:30 +0200	[thread overview]
Message-ID: <20230704091630.7db59243@maurocar-mobl2> (raw)
In-Reply-To: <20230626160106.2632928-4-bhanuprakash.modem@intel.com>

On Mon, 26 Jun 2023 21:31:05 +0530
Bhanuprakash Modem <bhanuprakash.modem@intel.com> wrote:

> Using wildcards in testplan configs, and keeping other configs
> (Xe & kms) in same dir may leads to the problem. Hence, exclude
> non-i915 tests from i915 testplan.

LGTM. Still, it needs to be applied before patch 1/4.

Reviewed-by: Mauro Carvalho Chehab <mchehab@kernel.org>

> 
> Cc: Mauro Carvalho Chehab <mauro.chehab@linux.intel.com>
> Signed-off-by: Bhanuprakash Modem <bhanuprakash.modem@intel.com>
> ---
>  tests/intel/i915_test_config.json | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/tests/intel/i915_test_config.json b/tests/intel/i915_test_config.json
> index 83317e65d..dda29bf9c 100644
> --- a/tests/intel/i915_test_config.json
> +++ b/tests/intel/i915_test_config.json
> @@ -10,7 +10,8 @@
>                 "../dumb_buffer.c", "../prime_vgem.c", "../sw_sync.c",
>                 "../syncobj_basic.c", "../syncobj_timeline.c", "../syncobj_wait.c",
>                 "../vgem_basic.c", "../vgem_slow.c" ],
> -    "exclude_files": [ "kms_*", "gem_concurrent_all.c", "gem_concurrent_blit.c" ],
> +    "exclude_files": [ "kms_*", "gem_concurrent_all.c", "gem_concurrent_blit.c",
> +                       "xe_*" ],
>      "fields": {
>  	"Mega feature": {
>                  "_properties_": {

  reply	other threads:[~2023-07-04  7:16 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-26 16:01 [igt-dev] [V3 i-g-t 0/4] New dir structure for intel specific tests Bhanuprakash Modem
2023-06-26 16:01 ` [igt-dev] [V3 i-g-t 1/4] tests: " Bhanuprakash Modem
2023-07-04  7:13   ` Mauro Carvalho Chehab
2023-08-03  5:52     ` Modem, Bhanuprakash
2023-06-26 16:01 ` [igt-dev] [V3 i-g-t 2/4] tests/intel/prime_mmap_kms: Add missing documentation Bhanuprakash Modem
2023-07-04  7:15   ` Mauro Carvalho Chehab
2023-06-26 16:01 ` [igt-dev] [V3 i-g-t 3/4] testplan/i915: Exclude non-i915 tests from i915 testplan Bhanuprakash Modem
2023-07-04  7:16   ` Mauro Carvalho Chehab [this message]
2023-06-26 16:01 ` [igt-dev] [V3 i-g-t 4/4] testplan/kms: Move kms testplan to intel dir Bhanuprakash Modem
2023-06-27 11:09   ` [igt-dev] [V2 " Bhanuprakash Modem
2023-07-04  7:14     ` Mauro Carvalho Chehab
2023-06-26 16:54 ` [igt-dev] ✗ Fi.CI.BAT: failure for New dir structure for intel specific tests (rev3) Patchwork
2023-06-27  3:56 ` [igt-dev] ✗ GitLab.Pipeline: warning for New dir structure for intel specific tests (rev4) Patchwork
2023-06-27  8:20 ` [igt-dev] ✗ Fi.CI.BAT: failure " Patchwork
2023-06-27  8:41   ` Modem, Bhanuprakash
2023-06-27 11:45     ` Yedireswarapu, SaiX Nandan
2023-06-27 11:34 ` Patchwork
2023-06-27 11:41 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2023-06-27 11:43 ` [igt-dev] ✓ Fi.CI.BAT: success for New dir structure for intel specific tests (rev3) Patchwork
2023-06-27 13:32 ` [igt-dev] ✗ Fi.CI.IGT: failure for New dir structure for intel specific tests (rev4) Patchwork
2023-06-27 22:09 ` [igt-dev] ✗ Fi.CI.IGT: failure for New dir structure for intel specific tests (rev3) Patchwork
2023-06-28 10:56 ` [igt-dev] ✗ GitLab.Pipeline: warning for New dir structure for intel specific tests (rev6) Patchwork
2023-06-28 11:31 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2023-06-29  1:41 ` [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=20230704091630.7db59243@maurocar-mobl2 \
    --to=mauro.chehab@linux.intel.com \
    --cc=bhanuprakash.modem@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