From: "Darrick J. Wong" <djwong@kernel.org>
To: djwong@kernel.org, zlang@redhat.com
Cc: kent.overstreet@linux.dev, tytso@mit.edu,
linux-xfs@vger.kernel.org, fstests@vger.kernel.org, guan@eryu.me
Subject: [PATCHSET v2 0/2] fstests: testing improvements
Date: Tue, 25 Jul 2023 18:56:39 -0700 [thread overview]
Message-ID: <169033659987.3222210.11071346898413396128.stgit@frogsfrogsfrogs> (raw)
Hi all,
Here's a couple of patches that improve the test framework itself. The
first patch adds a -smoketest option that will run the generic file IO
loop tests each for 4 minutes apiece. The goal here is to provide a
quick means for developers to check that their changes didn't cause
major problems.
The second patch adds kernel gcov coverage reporting if the kernel is
set up to record such information.
v2: move the gcov code to a separate file, document what -smoketest does
and who the target audience is
If you're going to start using this mess, you probably ought to just
pull from my git trees, which are linked below.
This is an extraordinary way to destroy everything. Enjoy!
Comments and questions are, as always, welcome.
--D
fstests git tree:
https://git.kernel.org/cgit/linux/kernel/git/djwong/xfstests-dev.git/log/?h=testing-improvements
---
README | 12 +++++++
check | 24 +++++++++++++-
common/gcov | 87 +++++++++++++++++++++++++++++++++++++++++++++++++++
doc/group-names.txt | 1 +
tests/generic/475 | 2 +
tests/generic/476 | 2 +
tests/generic/521 | 2 +
tests/generic/522 | 2 +
tests/generic/642 | 2 +
9 files changed, 128 insertions(+), 6 deletions(-)
create mode 100644 common/gcov
next reply other threads:[~2023-07-26 1:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-26 1:56 Darrick J. Wong [this message]
2023-07-26 1:56 ` [PATCH 1/2] check: add a -smoketest option Darrick J. Wong
2023-07-27 19:04 ` Theodore Ts'o
2023-07-26 1:56 ` [PATCH 2/2] check: generate gcov code coverage reports at the end of each section Darrick J. Wong
2023-07-27 14:57 ` Zorro Lang
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=169033659987.3222210.11071346898413396128.stgit@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=guan@eryu.me \
--cc=kent.overstreet@linux.dev \
--cc=linux-xfs@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=zlang@redhat.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