From: Daniel Wagner <dwagner@suse.de>
To: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Cc: linux-block@vger.kernel.org, linux-nvme@lists.infradead.org,
Chaitanya Kulkarni <chaitanyak@nvidia.com>,
Hannes Reinecke <hare@suse.de>, Daniel Wagner <dwagner@suse.de>
Subject: [PATCH blktests v1 0/3] add blkdev type environment variable
Date: Tue, 2 Apr 2024 12:03:19 +0200 [thread overview]
Message-ID: <20240402100322.17673-1-dwagner@suse.de> (raw)
During the last batch of refactoring I noticed that we could reduce the number
of tests a bit. There are tests which are almost identically except how the
target is configured, file vs block device backend.
By introducing a configure knob, we can drop the duplicates and even make some
of the tests a bit more versatile. Not all tests exists in file and block device
backend version. Thus we increase the test coverage with this series. And not
really surprising, there is a fallout. The nvme/028 test with file backend is
failing in my setup but I was not able to figure out where things go wrong yet.
I'll provide some logs later.
Daniel Wagner (3):
nvme/rc: add blkdev type environment variable
nvme/{007,009,011,013,015,020,024}: drop duplicate nvmet blkdev type
tests
nvme/{021,022,025,026,027,028}: do not hard code target blkdev type
Documentation/running-tests.md | 2 ++
tests/nvme/006 | 5 ++--
tests/nvme/007 | 28 --------------------
tests/nvme/007.out | 2 --
tests/nvme/008 | 4 +--
tests/nvme/009 | 36 -------------------------
tests/nvme/009.out | 3 ---
tests/nvme/010 | 4 +--
tests/nvme/011 | 39 ---------------------------
tests/nvme/011.out | 3 ---
tests/nvme/012 | 4 +--
tests/nvme/013 | 43 ------------------------------
tests/nvme/013.out | 3 ---
tests/nvme/014 | 4 +--
tests/nvme/015 | 48 ----------------------------------
tests/nvme/015.out | 4 ---
tests/nvme/019 | 4 +--
tests/nvme/020 | 40 ----------------------------
tests/nvme/020.out | 4 ---
tests/nvme/021 | 6 ++---
tests/nvme/022 | 6 ++---
tests/nvme/023 | 4 +--
tests/nvme/024 | 40 ----------------------------
tests/nvme/024.out | 2 --
tests/nvme/025 | 6 ++---
tests/nvme/026 | 6 ++---
tests/nvme/027 | 6 ++---
tests/nvme/028 | 6 ++---
tests/nvme/rc | 3 ++-
29 files changed, 36 insertions(+), 329 deletions(-)
delete mode 100755 tests/nvme/007
delete mode 100644 tests/nvme/007.out
delete mode 100755 tests/nvme/009
delete mode 100644 tests/nvme/009.out
delete mode 100755 tests/nvme/011
delete mode 100644 tests/nvme/011.out
delete mode 100755 tests/nvme/013
delete mode 100644 tests/nvme/013.out
delete mode 100755 tests/nvme/015
delete mode 100644 tests/nvme/015.out
delete mode 100755 tests/nvme/020
delete mode 100644 tests/nvme/020.out
delete mode 100755 tests/nvme/024
delete mode 100644 tests/nvme/024.out
--
2.44.0
next reply other threads:[~2024-04-02 10:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-02 10:03 Daniel Wagner [this message]
2024-04-02 10:03 ` [PATCH blktests v1 1/3] nvme/rc: add blkdev type environment variable Daniel Wagner
2024-04-02 10:03 ` [PATCH blktests v1 2/3] nvme/{007,009,011,013,015,020,024}: drop duplicate nvmet blkdev type tests Daniel Wagner
2024-04-02 10:03 ` [PATCH blktests v1 3/3] nvme/{021,022,025,026,027,028}: do not hard code target blkdev type Daniel Wagner
2024-04-02 10:10 ` [PATCH blktests v1 0/3] add blkdev type environment variable Daniel Wagner
2024-04-03 4:54 ` Shinichiro Kawasaki
2024-04-03 9:00 ` Daniel Wagner
2024-04-03 22:27 ` Chaitanya Kulkarni
2024-04-04 8:13 ` Daniel Wagner
2024-04-04 7:43 ` Shinichiro Kawasaki
2024-04-04 8:29 ` Daniel Wagner
2024-04-04 11:07 ` Shinichiro Kawasaki
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=20240402100322.17673-1-dwagner@suse.de \
--to=dwagner@suse.de \
--cc=chaitanyak@nvidia.com \
--cc=hare@suse.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=shinichiro.kawasaki@wdc.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).