From: Jeff Layton <jlayton@redhat.com>
To: steved@redhat.com
Cc: linux-nfs@vger.kernel.org
Subject: [PATCH 0/2] nfs-utils: add testing infrastructure to nfs-utils
Date: Wed, 16 Dec 2009 14:40:38 -0500 [thread overview]
Message-ID: <1260992440-8234-1-git-send-email-jlayton@redhat.com> (raw)
This set is the same as the one I sent a month or so ago, with some
small changes to account for header file changes in Chuck's tree. This
patchset depends on the patches that add libnsm.a to nfs-utils.
This patchset is intended as a starting point for an automated test
suite for nfs-utils. The idea here is to start simply and add a suite of
tests that we can run via "make check" -- the standard automake method
for running tests.
Clearly there are limits to what we can test without a multi-host test
harness. My hope is that this should help keep us from breaking basic
functionality by allowing us to test it in a very simple fashion. At
some point in the future we should also consider how to best handle
multi-machine testing, but I see that as complimenting this code rather
than replacing it.
For this set, the focus is on testing statd, which is particularly
susceptible to subtle breakage. Problems with it are often not noticed
until lock recovery breaks, and that may greatly lag the actual
breakage.
To faciitate statd testing, I've added a "statdtest" program that can
serve as a synthetic statd client and an NLM simulator. It's very
loosely based on the old statd simulator code. That program is dependent
on some of Chuck Lever's recent statd patches -- notably the ones that
break out common NSM code into libnsm.a.
For this initial drop, I'm just adding a single test that tests mon and
unmon functionality with statd. Adding more tests should fairly simple
to do.
Jeff Layton (2):
nfs-utils: introduce new statd testing simulator
nfs-utils: add initial tests for statd that run via "make check"
Makefile.am | 2 +-
configure.ac | 4 +-
tests/Makefile.am | 7 +
tests/statdtest/Makefile.am | 45 ++++
tests/statdtest/README | 12 +
tests/statdtest/nlm_sm_inter.x | 43 +++
tests/statdtest/statdtest.c | 464 ++++++++++++++++++++++++++++++++++
tests/t0001-statd-basic-mon-unmon.sh | 55 ++++
tests/test-lib.sh | 41 +++
9 files changed, 671 insertions(+), 2 deletions(-)
create mode 100644 tests/Makefile.am
create mode 100644 tests/statdtest/Makefile.am
create mode 100644 tests/statdtest/README
create mode 100644 tests/statdtest/nlm_sm_inter.x
create mode 100644 tests/statdtest/statdtest.c
create mode 100755 tests/t0001-statd-basic-mon-unmon.sh
create mode 100755 tests/test-lib.sh
next reply other threads:[~2009-12-16 19:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-16 19:40 Jeff Layton [this message]
2009-12-16 19:40 ` [PATCH 1/2] nfs-utils: introduce new statd testing simulator Jeff Layton
2009-12-16 19:40 ` [PATCH 2/2] nfs-utils: add initial tests for statd that run via "make check" Jeff Layton
2009-12-24 13:27 ` Steve Dickson
[not found] ` <4B336C25.7000705-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2009-12-25 0:20 ` Jeff Layton
[not found] ` <20091224192007.217a9ed5-PC62bkCOHzGdMjc06nkz3ljfA9RmPOcC@public.gmane.org>
2009-12-29 15:38 ` Chuck Lever
2009-12-29 16:09 ` Jeff Layton
-- strict thread matches above, loose matches on Subject: below --
2009-10-26 12:52 [PATCH 0/2] nfs-utils: add testing infrastructure to nfs-utils Jeff Layton
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=1260992440-8234-1-git-send-email-jlayton@redhat.com \
--to=jlayton@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=steved@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