From: "J. Bruce Fields" <bfields@fieldses.org>
To: Tigran Mkrtchyan <tigran.mkrtchyan@desy.de>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH 0/5] more test on current stateid processing
Date: Tue, 17 Jan 2012 11:42:05 -0500 [thread overview]
Message-ID: <20120117164205.GD13977@fieldses.org> (raw)
In-Reply-To: <1326654328-20557-1-git-send-email-tigran.mkrtchyan@desy.de>
Applied the pynfs changes, thanks!
--b.
On Sun, Jan 15, 2012 at 08:05:23PM +0100, Tigran Mkrtchyan wrote:
>
> This is the result of testing my changes in linux:
>
> $ ./testserver.py --maketree 192.168.178.20:/tmp currentstateid
> .....
>
> **************************************************
> CSID1 st_current_stateid.testOpenAndClose : PASS
> CSID2 st_current_stateid.testLockLockU : PASS
> CSID3 st_current_stateid.testOpenWriteClose : PASS
> CSID4 st_current_stateid.testLockWriteLocku : PASS
> CSID5 st_current_stateid.testOpenPutrootfhClose : PASS
> CSID6 st_current_stateid.testCloseNoStateid : PASS
> CSID7 st_current_stateid.testOpenLayoutGet : FAILURE
> OP_LAYOUTGET should return NFS4_OK, instead got
> NFS4ERR_NOTSUPP
> CSID8 st_current_stateid.testOpenSetattr : PASS
> CSID9 st_current_stateid.testOpenFreestateidClose : PA
>
> **************************************************
> $
>
> Tigran Mkrtchyan (5):
> client: move current stateid test into a dedicated module
> client: test current stateid processing on PUTROOTFH
> client: test current stateid processing with OPEN+LAYOUTGET in a
> single compound
> client: test current stateid processing with OPEN and SETATTR
> client: test OPEN+FREE_STETEID+CLOSE in a single compound
>
> nfs4.1/server41tests/__init__.py | 1 +
> nfs4.1/server41tests/st_current_stateid.py | 161 ++++++++++++++++++++++++++++
> nfs4.1/server41tests/st_open.py | 76 -------------
> 3 files changed, 162 insertions(+), 76 deletions(-)
> create mode 100644 nfs4.1/server41tests/st_current_stateid.py
>
> --
> 1.7.7.5
>
next prev parent reply other threads:[~2012-01-17 16:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-15 19:05 [PATCH 0/5] more test on current stateid processing Tigran Mkrtchyan
2012-01-15 19:05 ` [PATCH 1/5] client: move current stateid test into a dedicated module Tigran Mkrtchyan
2012-01-15 19:05 ` [PATCH 2/5] client: test current stateid processing on PUTROOTFH Tigran Mkrtchyan
2012-01-15 19:05 ` [PATCH 3/5] client: test current stateid processing with OPEN+LAYOUTGET in a single compound Tigran Mkrtchyan
2012-01-15 19:05 ` [PATCH 4/5] client: test current stateid processing with OPEN and SETATTR Tigran Mkrtchyan
2012-01-15 19:05 ` [PATCH 5/5] client: test OPEN+FREE_STETEID+CLOSE in a single compound Tigran Mkrtchyan
2012-01-15 20:54 ` [PATCH 0/5] more test on current stateid processing J. Bruce Fields
2012-01-15 22:31 ` Tiramisu Mokka
2012-01-17 16:42 ` J. Bruce Fields [this message]
2012-01-24 11:53 ` Benny Halevy
2012-01-24 12:18 ` Tigran Mkrtchyan
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=20120117164205.GD13977@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=tigran.mkrtchyan@desy.de \
/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.