linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bruce Fields <bfields@fieldses.org>
To: Frank Filz <ffilzlnx@mindspring.com>
Cc: linux-nfs@vger.kernel.org, "'J. Bruce Fields'" <bfields@redhat.com>
Subject: Re: [pynfs] [PATCH 3/3] Fix DELEG21 to have CODE:
Date: Thu, 29 Mar 2018 12:46:23 -0400	[thread overview]
Message-ID: <20180329164623.GB17806@fieldses.org> (raw)
In-Reply-To: <00e801d3c6e9$8ab47c00$a01d7400$@mindspring.com>

Uh, I think I didn't actually mean to commit that test at all.  Oh well,
I'll take this and then go see if I can find what else I had to patch to
make it work.

I realized after writing this that the existing tests all *require* that
clients' operations conflict with their own delegations.  So at some
point those tests need fixing too, but for now they're useful tests of
my patches--when they start failing I know I've got something right.

--b.

On Wed, Mar 28, 2018 at 04:07:27PM -0700, Frank Filz wrote:
> Signed-off-by: Frank S. Filz <ffilzlnx@mindspring.com>
> 
> ---
> 
> nfs4.0/servertests/st_delegation.py | 2 +-
> 
> 1 file changed, 1 insertion(+), 1 deletion(-)
> 
>  
> 
> diff --git a/nfs4.0/servertests/st_delegation.py
> b/nfs4.0/servertests/st_delegation.py
> 
> index e204e50..1d69fb5 100644
> 
> --- a/nfs4.0/servertests/st_delegation.py
> 
> +++ b/nfs4.0/servertests/st_delegation.py
> 
> @@ -714,7 +714,7 @@ def testServerSelfConflict(t, env):
> 
>      It should not conflict with the read delegation.
> 
>      FLAGS: delegations
> 
> -    DELEG21
> 
> +    CODE: DELEG21
> 
>      """
> 
>      c = env.c1
> 
>      count = c.cb_server.opcounts[OP_CB_RECALL]
> 
> -- 
> 
> 2.5.5
> 
>  
> 
>  
> 
>  
> 

           reply	other threads:[~2018-03-29 16:46 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <00e801d3c6e9$8ab47c00$a01d7400$@mindspring.com>]

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=20180329164623.GB17806@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=bfields@redhat.com \
    --cc=ffilzlnx@mindspring.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).