From: Lucas De Marchi <lucas.demarchi@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: mchehab@kernel.org, kamil.konieczny@linux.intel.com,
Janusz Krzysztofik <janusz.krzysztofik@linux.intel.com>,
Lucas De Marchi <lucas.demarchi@intel.com>
Subject: [PATCH i-g-t 2/2] tests/intel-ci/xe-fast-feedback: Add xe_mocs to kunit tests
Date: Wed, 7 Feb 2024 14:45:01 -0800 [thread overview]
Message-ID: <20240207224643.250958-2-lucas.demarchi@intel.com> (raw)
In-Reply-To: <20240207224643.250958-1-lucas.demarchi@intel.com>
xe_live_ktest@xe_mocs was added, but never included in the BAT tests. We
should really be checking mocs as BAT.
Signed-off-by: Lucas De Marchi <lucas.demarchi@intel.com>
---
tests/intel-ci/xe-fast-feedback.testlist | 1 +
1 file changed, 1 insertion(+)
diff --git a/tests/intel-ci/xe-fast-feedback.testlist b/tests/intel-ci/xe-fast-feedback.testlist
index 6c01374c1..82e02e3bd 100644
--- a/tests/intel-ci/xe-fast-feedback.testlist
+++ b/tests/intel-ci/xe-fast-feedback.testlist
@@ -231,6 +231,7 @@ igt@core_hotunplug@unbind-rebind
igt@xe_live_ktest@xe_bo
igt@xe_live_ktest@xe_dma_buf
igt@xe_live_ktest@xe_migrate
+igt@xe_live_ktest@xe_mocs
# Move fault_mode tests at the end to unblock execution
igt@xe_exec_fault_mode@twice-basic
--
2.43.0
next prev parent reply other threads:[~2024-02-07 22:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-07 22:45 [PATCH i-g-t 1/2] tests/intel/xe_live_ktest: Rename subtest to match suite Lucas De Marchi
2024-02-07 22:45 ` Lucas De Marchi [this message]
2024-02-08 11:27 ` [PATCH i-g-t 2/2] tests/intel-ci/xe-fast-feedback: Add xe_mocs to kunit tests Kamil Konieczny
2024-02-07 23:51 ` ✓ CI.xeBAT: success for series starting with [i-g-t,1/2] tests/intel/xe_live_ktest: Rename subtest to match suite Patchwork
2024-02-08 17:43 ` Lucas De Marchi
2024-02-08 0:06 ` ✓ Fi.CI.BAT: " Patchwork
2024-02-08 4:35 ` ✗ 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=20240207224643.250958-2-lucas.demarchi@intel.com \
--to=lucas.demarchi@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=janusz.krzysztofik@linux.intel.com \
--cc=kamil.konieczny@linux.intel.com \
--cc=mchehab@kernel.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