From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: Jakub Kolakowski <jakub1.kolakowski@intel.com>,
igt-dev@lists.freedesktop.org
Cc: Adam Miszczak <adam.miszczak@intel.com>,
Marcin Bernatowicz <marcin.bernatowicz@intel.com>,
Lukasz Laguna <lukasz.laguna@intel.com>
Subject: Re: [PATCH i-g-t] tests/intel-ci/xe.blocklist: Add SR-IOV tests
Date: Tue, 9 Jul 2024 14:39:24 +0200 [thread overview]
Message-ID: <e021610a-57dd-4990-9809-9413003eb631@intel.com> (raw)
In-Reply-To: <20240709112736.652364-1-jakub1.kolakowski@intel.com>
On 09.07.2024 13:27, Jakub Kolakowski wrote:
> Add SR-IOV tests to xe blocklist so that only desired tests will be run
> in CI.
> SR-IOV tests that should be running are as follows:
> - sriov_basic@enable-vfs-autoprobe-off (all dynamic subtests)
> - sriov_basic@enable-vfs-autoprobe-on@numvfs-all
I'm not sure that we want to keep this test above in CI as it is almost
like a stress-test, and test below will provide the same functional
coverage, without being a stress
> - sriov_basic@enable-vfs-bind-unbind-each@numvfs-all
> - sriov_basic@bind-unbind-vf@vf-1
> - sriov_basic@bind-unbind-vf@vf-last
IMO those two do not bring any additional coverage compared to above:
sriov_basic@enable-vfs-bind-unbind-each@numvfs-all
so lets drop them from the CI (and maybe consider killing them for good)
>
> Signed-off-by: Jakub Kolakowski <jakub1.kolakowski@intel.com>
> Cc: Adam Miszczak <adam.miszczak@intel.com>
> Cc: Marcin Bernatowicz <marcin.bernatowicz@intel.com>
> Cc: Lukasz Laguna <lukasz.laguna@intel.com>
> Cc: Michal Wajdeczko <Michal.Wajdeczko@intel.com>
> ---
> tests/intel-ci/xe.blocklist.txt | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/tests/intel-ci/xe.blocklist.txt b/tests/intel-ci/xe.blocklist.txt
> index 828baf324..57e550885 100644
> --- a/tests/intel-ci/xe.blocklist.txt
> +++ b/tests/intel-ci/xe.blocklist.txt
> @@ -83,3 +83,9 @@ igt@kms_prime@.*
> ##################################################################
> igt@kms_cursor_legacy@modeset-atomic-cursor-hotspot
> ##################################################################
> +# SR-IOV tests
> +##################################################################
> +igt@sriov_basic@enable-vfs-autoprobe-on@numvfs-(?!all).*
> +igt@sriov_basic@enable-vfs-bind-unbind-each@numvfs-(?!all).*
> +igt@sriov_basic@bind-unbind-vf@vf-(?!(1$|last)).*
> +##################################################################
next prev parent reply other threads:[~2024-07-09 12:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-09 11:27 [PATCH i-g-t] tests/intel-ci/xe.blocklist: Add SR-IOV tests Jakub Kolakowski
2024-07-09 12:21 ` ✓ CI.xeBAT: success for " Patchwork
2024-07-09 12:27 ` ✓ Fi.CI.BAT: " Patchwork
2024-07-09 12:39 ` Michal Wajdeczko [this message]
2024-07-09 13:58 ` ✓ Fi.CI.IGT: " Patchwork
2024-07-09 14:23 ` ✓ CI.xeFULL: " Patchwork
2024-07-10 9:05 ` [PATCH i-g-t] " Bernatowicz, Marcin
-- strict thread matches above, loose matches on Subject: below --
2024-07-09 13:42 Jakub Kolakowski
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=e021610a-57dd-4990-9809-9413003eb631@intel.com \
--to=michal.wajdeczko@intel.com \
--cc=adam.miszczak@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=jakub1.kolakowski@intel.com \
--cc=lukasz.laguna@intel.com \
--cc=marcin.bernatowicz@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