[NFS-Ganesha-Devel] Running pynfs on macOS

Quick update on macOS progress. I just uploaded 4 patches to Gerrit which (along with other build hacks, shared previously [1]) allow macOS to run the pynfs 4.0 suite without crashing. I thought I may be done with crash bugs, but I hit another one while editing an FSAL_MEM-backed file in Vim, and the pynfs 4.1 suite has at least one crash failure too (related to lock misuse, similar to the last 4 patches). I will continue to send patches for non-macOS-specific correctness bugs. The pynfs 4.0 suite still has failures [2]. I may not address these at all, depending on the root cause, since I'm not really concerned with FSAL_MEM in particular, since I plan to be writing my own FSAL backend. [1] https://github.com/matvore/nfs-ganesha [2] WRT5a st_write.testMaximumData : FAILURE READ did not correspond to WRITE with large dataset -- SATT18 st_setattr.testMixed : FAILURE Changing size from 0 to 10 and owner to b'65534' using stateid=0 should return NFS4_OK, instead got NFS4ERR_PERM -- SEC7 st_secinfo.testRPCSEC_GSS : FAILURE SECINFO returned mechanism list without RPCSEC_GSS -- OPEN30 st_open.testReplay : FAILURE non-replayed open should fail should return NFS4ERR_SHARE_DENIED, instead got NFS4_OK -- OPEN25 st_open.testDenyWrite1 : FAILURE OPEN with access==write on a write-denied file should return NFS4ERR_SHARE_DENIED, instead got NFS4_OK -- OPEN21 st_open.testDenyRead1 : FAILURE OPEN with access==read on a read-denied file should return NFS4ERR_SHARE_DENIED, instead got NFS4_OK -- WRT5a st_write.testMaximumData : FAILURE READ did not correspond to WRITE with large dataset -- SATT18 st_setattr.testMixed : FAILURE Changing size from 0 to 10 and owner to b'65534' using stateid=0 should return NFS4_OK, instead got NFS4ERR_PERM -- SEC7 st_secinfo.testRPCSEC_GSS : FAILURE SECINFO returned mechanism list without RPCSEC_GSS -- OPEN30 st_open.testReplay : FAILURE non-replayed open should fail should return NFS4ERR_SHARE_DENIED, instead got NFS4_OK -- OPEN25 st_open.testDenyWrite1 : FAILURE OPEN with access==write on a write-denied file should return NFS4ERR_SHARE_DENIED, instead got NFS4_OK -- OPEN21 st_open.testDenyRead1 : FAILURE OPEN with access==read on a read-denied file should return NFS4ERR_SHARE_DENIED, instead got NFS4_OK