Date: Fri, 8 Mar 2019 08:08:50 -0700 From: Alan Somers <asomers@freebsd.org> To: Enji Cooper <yaneurabeya@gmail.com> Cc: src-committers <src-committers@freebsd.org>, svn-src-projects@freebsd.org Subject: Re: svn commit: r344890 - projects/fuse2/tests/sys/fs/fuse Message-ID: <CAOtMX2gkCq%2BpidtcHrvrCRm-fGcEuud3_HG80=NfS1RSF6NnFA@mail.gmail.com> In-Reply-To: <D4DDF062-4D8B-43A4-A838-68FD05797B6D@gmail.com> References: <201903071812.x27ICYKc075837@repo.freebsd.org> <D4DDF062-4D8B-43A4-A838-68FD05797B6D@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Mar 8, 2019 at 8:06 AM Enji Cooper <yaneurabeya@gmail.com> wrote: > > > > On Mar 7, 2019, at 10:12, Alan Somers <asomers@freebsd.org> wrote: > > > > Author: asomers > > Date: Thu Mar 7 18:12:34 2019 > > New Revision: 344890 > > URL: https://svnweb.freebsd.org/changeset/base/344890 > > > > Log: > > fuse(4): add tests relating to open(2) flags > > > > Sponsored by: The FreeBSD Foundation > > Would it also make sense to test out FUSE with pjdfstest? > -Enji Absolutely! libfuse includes a passthrough filesystem as an example. I plan to run pjdfstest on that. However, I don't think it should be added to CI, just because the runtime is long and the ratio of coverage to runtime is poor. I think I'll run pjdfstest by hand for exploratory testing, and write minimal reproduction cases for any bugs that it finds. -Alan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOtMX2gkCq%2BpidtcHrvrCRm-fGcEuud3_HG80=NfS1RSF6NnFA>