Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mauro.chehab@linux.intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t] xe_live_ktest: remove wa from the testlist
Date: Thu, 10 Aug 2023 06:34:46 +0200	[thread overview]
Message-ID: <20230810063446.53936f12@maurocar-mobl2> (raw)
In-Reply-To: <20230810062350.71afd6eb@maurocar-mobl2>

On Thu, 10 Aug 2023 06:23:50 +0200
Mauro Carvalho Chehab <mauro.chehab@linux.intel.com> wrote:

> On Wed, 9 Aug 2023 09:00:28 -0600
> Lucas De Marchi <lucas.demarchi@intel.com> wrote:
> 
> > On Wed, Aug 09, 2023 at 04:48:45PM +0200, Mauro Carvalho Chehab wrote:  
> > >From: Mauro Carvalho Chehab <mchehab@kernel.org>
> > >
> > >The workaround selftest is not a live test. It is meant to run
> > >via kunit.py, as part of the driver-independent validation.    
> > 
> > s/driver-independent/device-independent/
> > 
> >   
> > >
> > >So, remove it from IGT.
> > >
> > >Cc: Lucas De Marchi <lucas.demarchi@intel.com>
> > >Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
> > >---
> > > tests/xe/xe_live_ktest.c | 1 -
> > > 1 file changed, 1 deletion(-)
> > >
> > >diff --git a/tests/xe/xe_live_ktest.c b/tests/xe/xe_live_ktest.c
> > >index f0cbf4f623bc..53cc8c186215 100644
> > >--- a/tests/xe/xe_live_ktest.c
> > >+++ b/tests/xe/xe_live_ktest.c
> > >@@ -40,7 +40,6 @@ static const struct kunit_tests live_tests[] = {
> > > 	{ "xe_migrate_test",	"migrate" },
> > > 	{ "xe_pci_test",	"pci" },
> > > 	{ "xe_rtp_test",	"rtp" },    
> > 
> > this on too, but could be a separate patch  
> 
> Do you mean xe_rtp_test? I'll send a separate patch for it.

Hmm... from the logs, both xe_pci ana xe_rtp are device-independent tests:

[08:16:01] =================== xe_pci (2 subtests) ====================
[08:16:01] [PASSED] xe_gmdid_graphics_ip
[08:16:01] [PASSED] xe_gmdid_media_ip
[08:16:01] ===================== [PASSED] xe_pci ======================
[08:16:01] ==================== xe_rtp (1 subtest) ====================
[08:16:01] ================== xe_rtp_process_tests  ===================
[08:16:01] [PASSED] coalesce-same-reg
[08:16:01] [PASSED] no-match-no-add
[08:16:01] [PASSED] no-match-no-add-multiple-rules
[08:16:01] [PASSED] two-regs-two-entries
[08:16:01] [PASSED] clr-one-set-other
[08:16:01] [PASSED] set-field
[08:16:01] [PASSED] conflict-duplicate
[08:16:01] [PASSED] conflict-not-disjoint
[08:16:01] [PASSED] conflict-reg-type
[08:16:01] ============== [PASSED] xe_rtp_process_tests ===============
[08:16:01] ===================== [PASSED] xe_rtp ======================

I'll place both altogether at the same patch.

Regards,
Mauro

  reply	other threads:[~2023-08-10  4:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-09 14:48 [igt-dev] [PATCH i-g-t] xe_live_ktest: remove wa from the testlist Mauro Carvalho Chehab
2023-08-09 15:00 ` Lucas De Marchi
2023-08-10  4:23   ` Mauro Carvalho Chehab
2023-08-10  4:34     ` Mauro Carvalho Chehab [this message]
2023-08-09 16:02 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2023-08-09 16:55 ` [igt-dev] ○ CI.xeBAT: info " Patchwork
2023-08-10 15:39 ` [igt-dev] ✓ Fi.CI.IGT: success " 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=20230810063446.53936f12@maurocar-mobl2 \
    --to=mauro.chehab@linux.intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=lucas.demarchi@intel.com \
    /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