From: "André Almeida" <andrealmeid@collabora.com>
To: linux-block@vger.kernel.org
Cc: osandov@fb.com, kernel@collabora.com, krisman@collabora.com,
"André Almeida" <andrealmeid@collabora.com>
Subject: [PATCH blktests v2 0/3] Add --config argument for custom config filenames
Date: Wed, 30 Oct 2019 19:27:04 -0300 [thread overview]
Message-ID: <20191030222707.10142-1-andrealmeid@collabora.com> (raw)
Instead of just using the default config file, one may also find useful to
specify which configuration file would like to use without editing the config
file, like this:
$ ./check --config=tests_nvme
...
$ ./check -c tests_scsi
This pull request solves this. This change means to be optional, in the sense
that the default behavior should not be modified and current setups will not be
affect by this. To check if this is true, I have done the following test:
- Print the value of variables $DEVICE_ONLY, $QUICK_RUN, $TIMEOUT,
$RUN_ZONED_TESTS, $OUTPUT, $EXCLUDE
- Run with the following setups:
- with a config file in the dir
- without a config file in the dir
- configuring using command line arguments
With both original code and with my changes, I validated that the values
remained the same. Then, I used the argument --config=test_config to check that
the values of variables are indeed changing.
This patchset add this feature, update the docs and fix a minor issue with a
command line argument. Also, I have changed "# shellcheck disable=SC1091" to
"# shellcheck source=/dev/null", since it seems the proper way to disable this
check according to shellcheck documentation[1].
Thanks,
André
Changes since v1:
- Reorder commit, so bug fix comes first
- Document multiple -c options behavior
[1] https://github.com/koalaman/shellcheck/wiki/SC1090#exceptions
This patch is also avaible at GitHub:
https://github.com/osandov/blktests/pull/56
André Almeida (3):
check: Make "device-only" option a valid option
check: Add configuration file option
Documentation: Add information about `--config` argument
Documentation/running-tests.md | 4 +++-
check | 30 +++++++++++++++++++++++++-----
2 files changed, 28 insertions(+), 6 deletions(-)
--
2.23.0
next reply other threads:[~2019-10-30 22:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-30 22:27 André Almeida [this message]
2019-10-30 22:27 ` [PATCH blktests v2 1/3] check: Make "device-only" option a valid option André Almeida
2019-10-30 22:27 ` [PATCH blktests v2 2/3] check: Add configuration file option André Almeida
2019-10-30 22:27 ` [PATCH blktests v2 3/3] Documentation: Add information about `--config` argument André Almeida
2019-11-13 20:20 ` [PATCH blktests v2 0/3] Add --config argument for custom config filenames 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=20191030222707.10142-1-andrealmeid@collabora.com \
--to=andrealmeid@collabora.com \
--cc=kernel@collabora.com \
--cc=krisman@collabora.com \
--cc=linux-block@vger.kernel.org \
--cc=osandov@fb.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.