public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Joel Granados <j.granados@samsung.com>
To: Luis Chamberlain <mcgrof@kernel.org>
Cc: <osandov@fb.com>, <joshi.k@samsung.com>, <anuj20.g@samsung.com>,
	<ankit.kumar@samsung.com>, <vincent.fu@samsung.com>,
	<ming.lei@redhat.com>, <linux-block@vger.kernel.org>
Subject: Re: [PATCH 2/6] tests/nvme: add new test for rand-read on the nvme character device
Date: Fri, 30 Dec 2022 11:37:13 +0100	[thread overview]
Message-ID: <20221230103713.sf7y77ds77473rl3@localhost> (raw)
In-Reply-To: <20221221103441.3216600-3-mcgrof@kernel.org>

[-- Attachment #1: Type: text/plain, Size: 2176 bytes --]

On Wed, Dec 21, 2022 at 02:34:37AM -0800, Luis Chamberlain wrote:
> This does basic rand-read testing of the character device of a
> conventional NVMe drive.
> 
> Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
> ---
>  tests/nvme/046     | 42 ++++++++++++++++++++++++++++++++++++++++++
>  tests/nvme/046.out |  2 ++
>  2 files changed, 44 insertions(+)
>  create mode 100755 tests/nvme/046
>  create mode 100644 tests/nvme/046.out
> 
> diff --git a/tests/nvme/046 b/tests/nvme/046
> new file mode 100755
> index 000000000000..3526ab9eedab
> --- /dev/null
> +++ b/tests/nvme/046
> @@ -0,0 +1,42 @@
> +#!/bin/bash
> +# SPDX-License-Identifier: GPL-3.0+
> +# Copyright (C) 2022 Luis Chamberlain <mcgrof@kernel.org>
> +#
> +# This does basic sanity test for the nvme character device. This is a basic
> +# test and if it fails it is probably very likely other nvme character device
> +# tests would fail.
> +#
> +. tests/nvme/rc
> +
> +DESCRIPTION="basic rand-read io_uring_cmd engine for nvme-ns character device"
> +QUICK=1
> +
> +requires() {
> +	_nvme_requires
> +	_have_fio
> +}
> +
> +device_requires() {
> +	_require_test_dev_is_nvme
> +}
> +
> +test_device() {
> +	echo "Running ${TEST_NAME}"
> +	local ngdev=${TEST_DEV/nvme/ng}
> +	local fio_args=(
> +		--size=1M
> +		--cmd_type=nvme
> +		--filename="$ngdev"
> +		--time_based
> +		--runtime=10
> +	) &&
> +	_run_fio_rand_iouring_cmd "${fio_args[@]}" >>"${FULL}" 2>&1 ||
> +	fail=true
> +
> +	if [ -z "$fail" ]; then
> +		echo "Test complete"
> +	else
> +		echo "Test failed"
> +		return 1
> +	fi
I see that several test have this structure, but would it not be better
to do:

"""
if [ -n "$fail" ]; then
  echo "Test failed"
  return 1
fi

return "Test complete"
"""

I point this out because I noticed that most nvme tests just set the
"test complete" string at the end of the test function.

> +}
> diff --git a/tests/nvme/046.out b/tests/nvme/046.out
> new file mode 100644
> index 000000000000..2b5fa6af63b1
> --- /dev/null
> +++ b/tests/nvme/046.out
> @@ -0,0 +1,2 @@
> +Running nvme/046
> +Test complete
> -- 
> 2.35.1
> 

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

  parent reply	other threads:[~2022-12-30 10:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-21 10:34 [PATCH 0/6] blktests: char device tests with iouring-cmd fio Luis Chamberlain
2022-12-21 10:34 ` [PATCH 1/6] common/fio: add helpers using io-uring cmd engine Luis Chamberlain
2022-12-30 10:10   ` Joel Granados
2022-12-21 10:34 ` [PATCH 2/6] tests/nvme: add new test for rand-read on the nvme character device Luis Chamberlain
2022-12-23 13:11   ` Kanchan Joshi
2022-12-23 15:56     ` Luis Chamberlain
2023-01-17  7:46       ` Kanchan Joshi
2022-12-30 10:37   ` Joel Granados [this message]
2023-01-03  5:48     ` Chaitanya Kulkarni
2022-12-21 10:34 ` [PATCH 3/6] tests/nvme: add new test for rand-write " Luis Chamberlain
2022-12-21 10:34 ` [PATCH 4/6] tests/nvme: add new test for optimal write " Luis Chamberlain
2022-12-21 10:34 ` [PATCH 5/6] tests/zbd: add new basic test for reading zone " Luis Chamberlain
2022-12-21 10:34 ` [PATCH 6/6] " Luis Chamberlain
2022-12-28  3:25 ` [PATCH 0/6] blktests: char device tests with iouring-cmd fio 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=20221230103713.sf7y77ds77473rl3@localhost \
    --to=j.granados@samsung.com \
    --cc=ankit.kumar@samsung.com \
    --cc=anuj20.g@samsung.com \
    --cc=joshi.k@samsung.com \
    --cc=linux-block@vger.kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=ming.lei@redhat.com \
    --cc=osandov@fb.com \
    --cc=vincent.fu@samsung.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