All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Dickson <SteveD@redhat.com>
To: Jeff Layton <jlayton@redhat.com>
Cc: chuck.lever@oracle.com, bfields@fieldses.org, linux-nfs@vger.kernel.org
Subject: Re: [PATCH 0/4] nfs-utils: add testing infrastructure to nfs-utils (try #6)
Date: Tue, 12 Jan 2010 07:25:54 -0500	[thread overview]
Message-ID: <4B4C6A52.9010209@RedHat.com> (raw)
In-Reply-To: <1262962563-5554-1-git-send-email-jlayton@redhat.com>



On 01/08/2010 09:55 AM, Jeff Layton wrote:
> This is an updated patchset for adding test infrastructure to nfs-utils.
> The main differences in this patchset are:
> 
> 1) some bugfixes in the statdb_dump program
> 
> 2) an extra check for root privs in the t0001 test. If the caller
> doesn't have root privs, then the test is skipped
> 
> 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 "nsm_client" 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 be fairly simple
> to do.
> 
> Jeff Layton (4):
>   nfs-utils: make private cookie to hex conversion a library routine
>   nfs-utils: introduce new statd testing simulator
>   nfs-utils: add statdb_dump utility
>   nfs-utils: add initial tests for statd that run via "make check"
> 
Committed...

steved.

      parent reply	other threads:[~2010-01-12 12:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-08 14:55 [PATCH 0/4] nfs-utils: add testing infrastructure to nfs-utils (try #6) Jeff Layton
2010-01-08 14:56 ` [PATCH 1/4] nfs-utils: make private cookie to hex conversion a library routine Jeff Layton
2010-01-08 14:56 ` [PATCH 2/4] nfs-utils: introduce new statd testing simulator Jeff Layton
2010-01-08 14:56 ` [PATCH 3/4] nfs-utils: add statdb_dump utility Jeff Layton
2010-01-08 14:56 ` [PATCH 4/4] nfs-utils: add initial tests for statd that run via "make check" Jeff Layton
2010-01-08 16:49   ` Chuck Lever
2010-01-08 16:56     ` Jeff Layton
     [not found]       ` <20100108115651.7a84a3c5-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2010-01-08 18:21         ` Chuck Lever
2010-01-08 16:59     ` J. Bruce Fields
2010-01-12 12:25 ` Steve Dickson [this message]

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=4B4C6A52.9010209@RedHat.com \
    --to=steved@redhat.com \
    --cc=bfields@fieldses.org \
    --cc=chuck.lever@oracle.com \
    --cc=jlayton@redhat.com \
    --cc=linux-nfs@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.