From: Marcin Bernatowicz <marcin.bernatowicz@linux.intel.com>
To: igt-dev@lists.freedesktop.org
Cc: jonathan.cavitt@intel.com,
Marcin Bernatowicz <marcin.bernatowicz@linux.intel.com>,
Adam Miszczak <adam.miszczak@linux.intel.com>,
Lukasz Laguna <lukasz.laguna@intel.com>,
Jakub Kolakowski <jakub1.kolakowski@intel.com>,
Michal Wajdeczko <Michal.Wajdeczko@intel.com>
Subject: [PATCH v2 i-g-t 1/2] tests/intel-ci/xe.blocklist: Blocklist SR-IOV stress tests
Date: Thu, 11 Jul 2024 15:58:57 +0200 [thread overview]
Message-ID: <20240711135858.975304-2-marcin.bernatowicz@linux.intel.com> (raw)
In-Reply-To: <20240711135858.975304-1-marcin.bernatowicz@linux.intel.com>
Blocklist certain sriov_basic tests identified as overly stressful or
time-consuming to be executed with all dynamic subtests at once.
However, these dynamic subtests can still be executed via testlists
(refer to the BAT example below).
Included in the blocklist to prevent simultaneous execution of all
dynamic subtests:
igt@sriov_basic@enable-vfs-autoprobe-on
igt@sriov_basic@enable-vfs-bind-unbind-each
igt@sriov_basic@bind-unbind-vf
Tests retained for execution:
BAT:
igt@sriov_basic@enable-vfs-autoprobe-off@numvfs-all
igt@sriov_basic@enable-vfs-autoprobe-on@numvfs-1
FULL:
igt@sriov_basic@enable-vfs-autoprobe-off
igt@sriov_basic@enable-vfs-bind-unbind-each-numvfs-all
Cc: Adam Miszczak <adam.miszczak@linux.intel.com>
Cc: Lukasz Laguna <lukasz.laguna@intel.com>
Cc: Jakub Kolakowski <jakub1.kolakowski@intel.com>
Cc: Michal Wajdeczko <Michal.Wajdeczko@intel.com>
Signed-off-by: Marcin Bernatowicz <marcin.bernatowicz@linux.intel.com>
---
tests/intel-ci/xe.blocklist.txt | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/tests/intel-ci/xe.blocklist.txt b/tests/intel-ci/xe.blocklist.txt
index 828baf324..f9ef612c4 100644
--- a/tests/intel-ci/xe.blocklist.txt
+++ b/tests/intel-ci/xe.blocklist.txt
@@ -83,3 +83,10 @@ igt@kms_prime@.*
##################################################################
igt@kms_cursor_legacy@modeset-atomic-cursor-hotspot
##################################################################
+# SR-IOV tests too stressful or time-consuming
+# to execute all dynamic subtests at once.
+##################################################################
+igt@sriov_basic@enable-vfs-autoprobe-on$
+igt@sriov_basic@enable-vfs-bind-unbind-each$
+igt@sriov_basic@bind-unbind-vf$
+##################################################################
--
2.31.1
next prev parent reply other threads:[~2024-07-11 13:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-11 13:58 [PATCH v2 i-g-t 0/2] Refactor sriov_basic test and blocklisting Marcin Bernatowicz
2024-07-11 13:58 ` Marcin Bernatowicz [this message]
2024-07-11 13:58 ` [PATCH v2 i-g-t 2/2] tests/sriov_basic: Extract enable-vfs-bind-unbind-each-numvfs-all subtest Marcin Bernatowicz
2024-07-11 14:01 ` [PATCH v2 i-g-t 0/2] Refactor sriov_basic test and blocklisting Cavitt, Jonathan
2024-07-11 15:04 ` ✗ Fi.CI.BUILD: failure for Refactor sriov_basic test and blocklisting (rev2) 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=20240711135858.975304-2-marcin.bernatowicz@linux.intel.com \
--to=marcin.bernatowicz@linux.intel.com \
--cc=Michal.Wajdeczko@intel.com \
--cc=adam.miszczak@linux.intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=jakub1.kolakowski@intel.com \
--cc=jonathan.cavitt@intel.com \
--cc=lukasz.laguna@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