[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAFd5g46D2KNmsH2qyt_HdWN3peT=HM+We2cgGV5SUzjL2jgSiA@mail.gmail.com>
Date: Tue, 10 Aug 2021 15:00:57 -0700
From: Brendan Higgins <brendanhiggins@...gle.com>
To: Christoph Hellwig <hch@....de>
Cc: Bart Van Assche <bvanassche@....org>,
Joel Becker <jlbec@...lplan.org>, linux-kernel@...r.kernel.org,
Bodo Stroesser <bostroesser@...il.com>,
"Martin K . Petersen" <martin.petersen@...cle.com>,
Yanko Kaneti <yaneti@...lera.com>
Subject: Re: [PATCH v4 3/3] configfs: Add unit tests
On Mon, Aug 9, 2021 at 7:59 AM Christoph Hellwig <hch@....de> wrote:
>
> > text and binary attribute support. This is how I run these tests:
> >
> > set -e
> > if [ -e .config ]; then
> > make ARCH=um mrproper
> > fi
> > if [ ! -e .kunit/.kunitconfig ]; then
> > cat <<EOF >.kunit/.kunitconfig
> > CONFIG_CONFIGFS_FS=y
> > CONFIG_CONFIGFS_KUNIT_TEST=y
> > CONFIG_KUNIT=y
> > CONFIG_PROVE_LOCKING=y
> > CONFIG_SYSFS=y
> > CONFIG_UBSAN=y
> > EOF
> > cp .kunit/.kunitconfig .kunit/.config
> > fi
> > ./tools/testing/kunit/kunit.py run
>
> This is very useful documentation, but shouldn't it go into a README.kunit
> or similar instead of a commit message?
You could also put this in a .kunitconfig specific to your subsystem
like we did for ext4:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/fs/ext4/.kunitconfig
You can then build using this .kunitconfig with something like:
./tools/testing/kunit/kunit.py run --kunitconfig=fs/ext4/.kunitconfig
> > +config CONFIGFS_KUNIT_TEST
> > + bool "Configfs Kunit test" if !KUNIT_ALL_TESTS
> > + depends on CONFIGFS_FS && KUNIT=y
> > + default KUNIT_ALL_TESTS
Cheers!
Powered by blists - more mailing lists