From: nakshtra.goyal@intel.com
To: igt-dev@lists.freedesktop.org, ramadevi.gandi@intel.com
Cc: janga.rahul.kumar@intel.com, sai.gowtham.ch@intel.com
Subject: [PATCH i-g-t, v4 2/2] HAX/DO_NOT_MERGE: xe-fast-feedback: test xe_sysfs_preempt_timeout
Date: Wed, 31 Jul 2024 20:00:29 +0530 [thread overview]
Message-ID: <20240731143029.3661149-3-nakshtra.goyal@intel.com> (raw)
In-Reply-To: <20240731143029.3661149-1-nakshtra.goyal@intel.com>
From: Nakshtra Goyal <nakshtra.goyal@intel.com>
Test solution which should allow igt runner to properly
classify xe_sysfs_preempt_timeout, so adding it into
xe BAT runs
Signed-off-by: Nakshtra Goyal <nakshtra.goyal@intel.com>
---
tests/intel-ci/fast-feedback.testlist | 2 ++
1 file changed, 2 insertions(+)
diff --git a/tests/intel-ci/fast-feedback.testlist b/tests/intel-ci/fast-feedback.testlist
index be0965110..6316cc99e 100644
--- a/tests/intel-ci/fast-feedback.testlist
+++ b/tests/intel-ci/fast-feedback.testlist
@@ -1,6 +1,8 @@
# Try to load the driver if it's not available yet.
igt@i915_module_load@load
+igt@xe_sysfs_preempt_timeout@preempt_timeout_us-timeout
+
# Keep alphabetically sorted by default
igt@core_auth@basic-auth
igt@debugfs_test@read_all_entries
--
2.34.1
next prev parent reply other threads:[~2024-07-31 14:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-31 14:30 [PATCH i-g-t, v4 0/2] tests/intel/xe_sysfs_preempt_timeout: Porting sysfs preempt test in xe nakshtra.goyal
2024-07-31 14:30 ` [PATCH i-g-t, v4 1/2] " nakshtra.goyal
2024-08-01 14:10 ` Riana Tauro
2024-07-31 14:30 ` nakshtra.goyal [this message]
2024-07-31 14:53 ` ✗ GitLab.Pipeline: warning for tests/intel/xe_sysfs_preempt_timeout: Porting sysfs preempt test in xe (rev4) Patchwork
2024-07-31 15:05 ` ✓ CI.xeBAT: success " Patchwork
2024-07-31 15:19 ` ✗ Fi.CI.BAT: failure " Patchwork
2024-07-31 17:12 ` ✗ CI.xeFULL: " 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=20240731143029.3661149-3-nakshtra.goyal@intel.com \
--to=nakshtra.goyal@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=janga.rahul.kumar@intel.com \
--cc=ramadevi.gandi@intel.com \
--cc=sai.gowtham.ch@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