Date: Fri, 1 Mar 2019 16:28:42 -0800 From: Enji Cooper <yaneurabeya@gmail.com> To: Alan Somers <asomers@freebsd.org> Cc: src-committers@freebsd.org, svn-src-projects@freebsd.org Subject: Re: svn commit: r344715 - in projects/fuse2: etc/mtree tests/sys/fs tests/sys/fs/fuse Message-ID: <D66DB53E-CC5B-4EA4-95BD-6C96DEB50806@gmail.com> In-Reply-To: <201903012353.x21Nr5do051752@repo.freebsd.org> References: <201903012353.x21Nr5do051752@repo.freebsd.org>
index | next in thread | previous in thread | raw e-mail
> On Mar 1, 2019, at 15:53, Alan Somers <asomers@freebsd.org> wrote: > > Author: asomers > Date: Fri Mar 1 23:53:05 2019 > New Revision: 344715 > URL: https://svnweb.freebsd.org/changeset/base/344715 > > Log: > Begin a fuse(4) test suite > > It only tests the kernel portion of fuse, not the userspace portion (which > comes from sysutils/fusefs-libs). The kernel-userspace interface is > de-facto standardized, and this test suite seeks to validate FreeBSD's > implementation. > > It uses GoogleMock to substitute for a userspace daemon and validate the > kernel's behavior in response to filesystem access. GoogleMock is > convenient because it can validate the order, number, and arguments of each > operation, and return canned responses. > > But that also means that the test suite must use GoogleTest, since > GoogleMock is incompatible with atf-c++ and atf.test.mk does not allow C++ > programs to use atf-c. > > This commit adds the first 10 test cases out of an estimated 130 total. > > PR: 235775, 235773 Hi Alan! Could you please use SetupEnvironment to ensure that /dev/fuse exists and is accessible? This is something I needing to be done with the zfsd tests too, IIRC. Thanks so much :)!! -Enjihelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?D66DB53E-CC5B-4EA4-95BD-6C96DEB50806>