From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH v3 0/2] btrfs-progs: tests: Enahance INSTRUMENT coverage
Date: Tue, 7 Apr 2020 15:18:43 +0800 [thread overview]
Message-ID: <20200407071845.29428-1-wqu@suse.com> (raw)
This patchset will enhance INSTRUMENT coverage for all btrfs related
commands.
Since now INSTRUMENT would also cover a lot of btrfs inspect-dump
comands, fix some test cases where INSTRUMENT output could easily
pollute them.
Now fsck/convert/misc/mkfs all pass with
INSTRUMENT="valgrind --leak-check=full".
Changelog:
v2:
- Pass INSTRUMENT as space split command
- Unset previous cmmd_array in expand_command()
Instead of unsetting it.
- Use local variable @i in expand_command()
To fix misc/004
- Add extra commands for INSTRUMENT coverage
This incldues btrfstune, btrfs-corrupt-block, btrfs-image,
btrfs-select-super, btrfs-find-root.
- Fix test cases which uses run_check_stdout without filtering
v3:
- Adding proper filtering for run_check_stdout() callers
Instead of removing run_check_stdout(), to keep the coverage the same.
Qu Wenruo (2):
btrfs-progs: tests: Filter output for run_check_stdout
btrfs-progs: tests: Introduce expand_command() to inject aruguments
more accurately
tests/common | 189 +++++++++---------
tests/misc-tests/004-shrink-fs/test.sh | 11 +-
.../009-subvolume-sync-must-wait/test.sh | 2 +-
.../013-subvolume-sync-crash/test.sh | 2 +-
.../024-inspect-internal-rootid/test.sh | 21 +-
.../031-qgroup-parent-child-relation/test.sh | 4 +-
6 files changed, 120 insertions(+), 109 deletions(-)
--
2.26.0
next reply other threads:[~2020-04-07 7:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-07 7:18 Qu Wenruo [this message]
2020-04-07 7:18 ` [PATCH v3 1/2] btrfs-progs: tests: Filter output for run_check_stdout Qu Wenruo
2020-04-09 15:52 ` David Sterba
2020-04-10 0:25 ` Qu Wenruo
2020-04-20 23:09 ` David Sterba
2020-04-07 7:18 ` [PATCH v3 2/2] btrfs-progs: tests: Introduce expand_command() to inject aruguments more accurately Qu Wenruo
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=20200407071845.29428-1-wqu@suse.com \
--to=wqu@suse.com \
--cc=linux-btrfs@vger.kernel.org \
/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.