From: Petr Vorel <pvorel@suse.cz>
To: "J. Bruce Fields" <bfields@redhat.com>
Cc: linux-nfs@vger.kernel.org, Yong Sun <yosun@suse.com>
Subject: Re: pynfs: COUR2, EID50 test failures
Date: Sun, 23 May 2021 21:14:37 +0200 [thread overview]
Message-ID: <YKqpnXjGP+Ub0lB0@pevik> (raw)
In-Reply-To: <YKf+a7e4lv2BwBBQ@pick.fieldses.org>
> On Fri, May 21, 2021 at 08:47:01AM +0200, Petr Vorel wrote:
> > Hi Bruce,
> > what's wrong with pynfs COUR2, EID50 tests?
> > They're failing on various kernels.
> > I got these failures on 5.11.12 (openSUSE package), 5.13.0-rc2 (mainline on
> > openSUSE), 4.9.0 (Debian package):
> > COUR2 st_courtesy.testLockSleepLock : FAILURE
> > OP_OPEN should return NFS4_OK, instead got
> > NFS4ERR_GRACE
> Are you running it immediately after starting the server? If so, that's
> expected. Personally my test scripts mount the server and create a file
> there before running pynfs tests. The create won't return until the
> grace period's done.
Thanks for info, I'll test that!
> Might be worth documenting in the README, or teaching pynfs to wait
> before running tests.
Or maybe test should create a test file before? That might be faster than waiting.
Because there is some wait for 2 min as part of testing.
> > EID50 st_exchange_id.testSSV : FAILURE
> > nfs4lib.NFS4Error: OP_EXCHANGE_ID should return
> > NFS4_OK, instead got NFS4ERR_ENCR_ALG_UNSUPP
> > Nothing in dmesg (tested with "rpcdebug -m nfsd -s lockd").
> > Or is it just my wrong setup?
> SSV support is optional. We should probably drop the "all" tag from
> that test.
Again, thanks for info. It'd be great if you implement that.
Kind regards,
Petr
> --b.
next prev parent reply other threads:[~2021-05-23 19:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-21 6:47 pynfs: COUR2, EID50 test failures Petr Vorel
2021-05-21 18:39 ` J. Bruce Fields
2021-05-23 19:14 ` Petr Vorel [this message]
2021-05-24 8:19 ` Petr Vorel
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=YKqpnXjGP+Ub0lB0@pevik \
--to=pvorel@suse.cz \
--cc=bfields@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=yosun@suse.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