Date: Fri, 1 Mar 2019 21:20:29 -0800 From: Enji Cooper <yaneurabeya@gmail.com> To: Alan Somers <asomers@freebsd.org> Cc: src-committers <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: <73B429B3-BC33-4A2C-88FA-8813EDF2C2D9@gmail.com> In-Reply-To: <CAOtMX2hfYYexvV8iCN%2Bzib-k7M4RiH4XtbBc22EGEfp-4L5azQ@mail.gmail.com> References: <201903012353.x21Nr5do051752@repo.freebsd.org> <D66DB53E-CC5B-4EA4-95BD-6C96DEB50806@gmail.com> <CAOtMX2hfYYexvV8iCN%2Bzib-k7M4RiH4XtbBc22EGEfp-4L5azQ@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
> On Mar 1, 2019, at 4:37 PM, Alan Somers <asomers@freebsd.org> wrote: … > What's the advantage to doing it that way as opposed to using the > regular SetUp function? SetupEnvironment is only executed once per test suite; SetUp is executed once per test case, so multiple times per test suite. Running SetupEnvironment is an obvious performance win for something that is unlikely to change over the course of a test suite’s execution. HTH! -Enjihelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?73B429B3-BC33-4A2C-88FA-8813EDF2C2D9>