selftests/filesystems: Don't run dnotify_test by default
authorMichael Ellerman <mpe@ellerman.id.au>
Tue, 10 Apr 2018 06:20:53 +0000 (16:20 +1000)
committerShuah Khan <shuahkh@osg.samsung.com>
Tue, 17 Apr 2018 23:01:16 +0000 (17:01 -0600)
commit8bf24e8319613bbe950d4188682b3a0d9441b76b
tree826c7a85f0d8478a4d610d24c6b462933aa33a37
parent60cc43fc888428bb2f18f08997432d426a243338
selftests/filesystems: Don't run dnotify_test by default

In commit ce290a19609d ("selftests: add devpts selftests"), the
filesystems directory was added to the top-level selftests Makefile.

That had the effect of causing the existing dnotify_test in the
filesystems directory to now be run as part of the default selftests
test-run. Unfortunately dnotify_test is actually an infinite loop.

Fix it by moving dnotify_test to TEST_GEN_PROGS_EXTENDED, which says
that it's a generated file (ie. built) but should not be run as part
of the default test suite run (it's an "extended" test).

While we're here cleanup a few other things, devpts_pts should be in
TEST_GEN_PROGS to indicate that it's built, and with the above two
changes we no longer need a custom all or clean rule.

Fixes: ce290a19609d ("selftests: add devpts selftests")
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Acked-by: Christian brauner <christian.brauner@ubuntu.com>
Signed-off-by: Shuah Khan <shuahkh@osg.samsung.com>
tools/testing/selftests/filesystems/Makefile