From: Omar Sandoval <osandov@osandov.com>
To: Sagi Grimberg <sagi@grimberg.me>
Cc: linux-block@vger.kernel.org, linux-nvme@lists.infradead.org,
Logan Gunthorpe <logang@deltatee.com>,
Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>,
Keith Busch <kbusch@kernel.org>, Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH v7 4/7] tests/nvme: restrict tests to specific transports
Date: Mon, 14 Sep 2020 14:53:47 -0700 [thread overview]
Message-ID: <20200914215347.GB148663@relinquished.localdomain> (raw)
In-Reply-To: <20200903235337.527880-5-sagi@grimberg.me>
On Thu, Sep 03, 2020 at 04:53:34PM -0700, Sagi Grimberg wrote:
> Protect against running tests with the wrong transport type. Most tests
> cannot have nvme_trtype=nvme and discovery tests expect the $trtype to
> be written and verified in the .out file. Adding a couple of helpers
> to restrict the transport types in tests.
>
> Signed-off-by: Sagi Grimberg <sagi@grimberg.me>
> ---
> tests/nvme/002 | 1 +
> tests/nvme/003 | 1 +
> tests/nvme/004 | 1 +
> tests/nvme/005 | 1 +
> tests/nvme/006 | 1 +
> tests/nvme/007 | 1 +
> tests/nvme/008 | 1 +
> tests/nvme/009 | 1 +
> tests/nvme/010 | 1 +
> tests/nvme/011 | 1 +
> tests/nvme/012 | 1 +
> tests/nvme/013 | 1 +
> tests/nvme/014 | 1 +
> tests/nvme/015 | 1 +
> tests/nvme/016 | 1 +
> tests/nvme/017 | 1 +
> tests/nvme/018 | 1 +
> tests/nvme/019 | 1 +
> tests/nvme/020 | 1 +
> tests/nvme/021 | 1 +
> tests/nvme/022 | 1 +
> tests/nvme/023 | 1 +
> tests/nvme/024 | 1 +
> tests/nvme/025 | 1 +
> tests/nvme/026 | 1 +
> tests/nvme/027 | 1 +
> tests/nvme/028 | 1 +
> tests/nvme/029 | 1 +
> tests/nvme/030 | 1 +
> tests/nvme/031 | 1 +
> tests/nvme/rc | 16 ++++++++++++++++
> 31 files changed, 46 insertions(+)
>
> diff --git a/tests/nvme/002 b/tests/nvme/002
> index 955f68da026a..ca11c11c9a09 100755
> --- a/tests/nvme/002
> +++ b/tests/nvme/002
> @@ -12,6 +12,7 @@ DESCRIPTION="create many subsystems and test discovery"
> requires() {
> _nvme_requires
> _have_modules loop
> + _require_nvme_trtype_is_loop
Same comment here, chain these with &&.
next prev parent reply other threads:[~2020-09-14 21:53 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-03 23:53 [PATCH v7 0/7] blktests: Add support to run nvme tests with tcp/rdma transports Sagi Grimberg
2020-09-03 23:53 ` [PATCH v7 1/7] nvme: consolidate nvme requirements based on transport type Sagi Grimberg
2020-09-04 0:18 ` Chaitanya Kulkarni
2020-09-14 21:51 ` Omar Sandoval
2020-09-14 22:04 ` Logan Gunthorpe
2020-09-14 22:09 ` Omar Sandoval
2020-09-14 22:23 ` Logan Gunthorpe
2020-09-14 22:25 ` Omar Sandoval
2020-09-03 23:53 ` [PATCH v7 2/7] nvme: consolidate some nvme-cli utility functions Sagi Grimberg
2020-09-04 0:19 ` Chaitanya Kulkarni
2020-09-03 23:53 ` [PATCH v7 3/7] nvme: make tests transport type agnostic Sagi Grimberg
2020-09-04 0:20 ` Chaitanya Kulkarni
2020-09-03 23:53 ` [PATCH v7 4/7] tests/nvme: restrict tests to specific transports Sagi Grimberg
2020-09-04 0:21 ` Chaitanya Kulkarni
2020-09-14 21:53 ` Omar Sandoval [this message]
2020-09-03 23:53 ` [PATCH v7 5/7] nvme: support nvme-tcp when runinng tests Sagi Grimberg
2020-09-04 0:21 ` Chaitanya Kulkarni
2020-09-03 23:53 ` [PATCH v7 6/7] common: move module_unload to common Sagi Grimberg
2020-09-04 0:22 ` Chaitanya Kulkarni
2020-09-03 23:53 ` [PATCH v7 7/7] nvme: support rdma transport type Sagi Grimberg
2020-09-04 0:23 ` Chaitanya Kulkarni
2020-09-04 17:00 ` Yi Zhang
2020-09-04 15:52 ` [PATCH v7 0/7] blktests: Add support to run nvme tests with tcp/rdma transports Logan Gunthorpe
2020-09-11 22:06 ` Sagi Grimberg
2020-09-25 17:32 ` Omar Sandoval
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=20200914215347.GB148663@relinquished.localdomain \
--to=osandov@osandov.com \
--cc=Chaitanya.Kulkarni@wdc.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=logang@deltatee.com \
--cc=sagi@grimberg.me \
/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