Yes, those failures are expected.

SEQ6 really should be changed to either expect either error, or since it’s really trying to trigger NFS4ERR_REQ_TOO_BIG it should do something else besides an overly long name to create the error (Ganesha detects the too long name during XDR before it gets to the COMPOUND processing to decide the request size is too big).

CSESS20 and CSESS21 are callback issues, someone should look into those. I don’t recall what my investigation showed.

I also forget what my investigation of EID50 showed.

Frank

From: Trishali Nayar [mailto:ntrishal@in.ibm.com]
Sent: Wednesday, June 3, 2020 7:04 AM
To: devel@lists.nfs-ganesha.org
Subject: [NFS-Ganesha-Devel] pynfs tests on 4.1

Hi all,

While running pynfs test suite with 4.1, we observed that few tests failed:-

1> SEQ6 st_sequence.testRequestTooBig : FAILURE
OP_LOOKUP should return NFS4ERR_REQ_TOO_BIG, instead
got NFS4ERR_NAMETOOLONG

2> CSESS21 st_create_session.testCallbackVersion : FAILURE
No CB_NULL sent

3> CSESS20 st_create_session.testCallbackProgram : FAILURE
No CB_NULL sent

4> EID50 st_exchange_id.testSSV : FAILURE
AttributeError: 'ClientStateProtection' object has no
attribute 'context'

Are these failures expected i.e. we know about them and its not actually a problem OR are these issues that need to be fixed?

Pls. let us know your inputs on same.

Thanks and regards,
Trishali.