linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bfields@fieldses.org (J. Bruce Fields)
To: Frank Filz <ffilzlnx@mindspring.com>
Cc: Kernel NFS List <linux-nfs@vger.kernel.org>,
	"'J. Bruce Fields'" <bfields@redhat.com>
Subject: Re: [pynfs] [PATCH 2/3] Remove ganesha tag from DSESS9002 and DSESS9003
Date: Thu, 29 Mar 2018 12:47:02 -0400	[thread overview]
Message-ID: <20180329164702.GC17806@fieldses.org> (raw)
In-Reply-To: <00e301d3c6e9$76f406e0$64dc14a0$@mindspring.com>

On Wed, Mar 28, 2018 at 04:06:54PM -0700, Frank Filz wrote:
> These tests actually require operational delegations which are not
> 
> generally available in Ganesha. With the fixedup tests, they now
> 
> hang without delegation support.

OK, thanks.--b.

> 
>  
> 
> Signed-off-by: Frank S. Filz <ffilzlnx@mindspring.com>
> 
> ---
> 
> nfs4.1/server41tests/st_destroy_session.py | 4 ++--
> 
> 1 file changed, 2 insertions(+), 2 deletions(-)
> 
>  
> 
> diff --git a/nfs4.1/server41tests/st_destroy_session.py
> b/nfs4.1/server41tests/st_destroy_session.py
> 
> index c247434..c48d144 100644
> 
> --- a/nfs4.1/server41tests/st_destroy_session.py
> 
> +++ b/nfs4.1/server41tests/st_destroy_session.py
> 
> @@ -39,7 +39,7 @@ def testDestroy2(t, env):
> 
>       tests for example)
> 
>     - check that we get the callback
> 
> -    FLAGS: destroy_session ganesha
> 
> +    FLAGS: destroy_session
> 
>      CODE: DSESS9002
> 
>      """
> 
>      recall = threading.Event()
> 
> @@ -88,7 +88,7 @@ def testDestroy3(t, env):
> 
>     - check that a new callback is sent over the new session.  Some
> 
>       servers will do this very quickly, some might take longer.
> 
> -    FLAGS: destroy_session ganesha
> 
> +    FLAGS: destroy_session
> 
>      CODE: DSESS9003
> 
>      """
> 
>      recall = threading.Event()
> 
> -- 
> 
> 2.5.5
> 
>  
> 
>  
> 
>  
> 

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

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <00e301d3c6e9$76f406e0$64dc14a0$@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=20180329164702.GC17806@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).