summaryrefslogtreecommitdiffstats
path: root/share/doc
diff options
context:
space:
mode:
authorngie <ngie@FreeBSD.org>2014-12-05 11:44:18 +0000
committerngie <ngie@FreeBSD.org>2014-12-05 11:44:18 +0000
commit2ceba1b1340a12cfe78aa2589bb0bba87f7b33d9 (patch)
treee08795fd1d98cb1be488d6510c6b57e60398f2fa /share/doc
parentf88754a36c36675f66d041b57d0da1b2ea102c62 (diff)
downloadFreeBSD-src-2ceba1b1340a12cfe78aa2589bb0bba87f7b33d9.zip
FreeBSD-src-2ceba1b1340a12cfe78aa2589bb0bba87f7b33d9.tar.gz
MFC r272057,r272083,r272084,r272087,r274016:
r272057: Import pjdfstest from ^/vendor/pjdfstest/abf03c3a47745d4521b0e4aa141317553ca48f91 - Remove tools/regression/pjdfstest - Add upgrade directions for contrib/pjdfstest - Add a note to UPDATING for the move (the reachover Makefiles are coming soon) Functional differences: - ftruncate testcases are added from upstream (github) Non-functional differences: - The copyright for the project has been updated to 2012 - pjd's contact information has been updated Discussed with: -testing, jmmv, pjd Sponsored by: EMC / Isilon Storage Division r272083: Expect ELOOP on Darwin/Linux with "O_NOFOLLOW was specified and the target is a symbolic link" case. Assume EMLINK on the rest of the OSes (FreeBSD, Solaris, etc) Sponsored by: EMC / Isilon Storage Division r272084: Fix the executed testplan count Sponsored by: EMC / Isilon Storage Division r272087: Increase the memory disk size in the following testcases to avoid mount failures, which would cause cascade failures in the rest of the test run: link/15.t, open/19.t, mkdir/11.t, mkfifo/11.t, symlink/11.t Fail quickly in all of the testcases if mdconfig, mount, umount, etc fails to avoid issues similar to this in the future Submitted by: Casey Peel <cpeel@isilon.com> Sponsored by: EMC / Isilon Storage Division r274016: Integrate pjdfstest test suite execution into kyua pjdfstest execution is opt-in and must be done as root due to some of the assumptions made by the test suite and lack of error checking in the non-root case A description of how to execute pjdfstest with kyua is provided in share/pjdfstest/README Phabric: D824 (an earlier prototype patch) Relnotes: yes Sponsored by: EMC / Isilon Storage Division
Diffstat (limited to 'share/doc')
-rw-r--r--share/doc/Makefile2
-rw-r--r--share/doc/pjdfstest/Makefile8
-rw-r--r--share/doc/pjdfstest/README36
3 files changed, 46 insertions, 0 deletions
diff --git a/share/doc/Makefile b/share/doc/Makefile
index a4fe61d..d01a2b2 100644
--- a/share/doc/Makefile
+++ b/share/doc/Makefile
@@ -7,10 +7,12 @@ SUBDIR= ${_IPv6} \
${_atf} \
legal \
${_llvm} \
+ ${_pjdfstest} \
${_roffdocs}
.if ${MK_TESTS} != "no"
_atf= atf
+_pjdfstest= pjdfstest
.endif
.if ${MK_CLANG} != "no"
diff --git a/share/doc/pjdfstest/Makefile b/share/doc/pjdfstest/Makefile
new file mode 100644
index 0000000..21d72f3
--- /dev/null
+++ b/share/doc/pjdfstest/Makefile
@@ -0,0 +1,8 @@
+# $FreeBSD$
+
+NO_OBJ=
+
+FILESDIR= ${SHAREDIR}/doc/pjdfstest
+FILES= README
+
+.include <bsd.prog.mk>
diff --git a/share/doc/pjdfstest/README b/share/doc/pjdfstest/README
new file mode 100644
index 0000000..d090117
--- /dev/null
+++ b/share/doc/pjdfstest/README
@@ -0,0 +1,36 @@
+pjdfstest test suite execution is integrated into kyua. This README describes
+how to use pjdfstest in the default configuration (kyua work directory), and
+with a specific filesystem path.
+
+Method 1. Executing with default configuration (kyua work directory)
+
+ 1. Elevate privileges:
+ % su -
+ 2. cd to the tests directory:
+ % cd /usr/tests/sys/pjdfstest
+ 3. Run kyua:
+ % kyua test
+
+ Executing the commands as shown above will run pjdfstest in the kyua work
+ directory. The kyua work directory defaults to a random generated path under
+ /tmp; please see TMPDIR in kyua(1) for more details on how the temporary path
+ is chosen with kyua.
+
+Method 2. Executing with a specific filesystem path (in this case /mnt)
+
+ 1. Elevate privileges:
+ % su -
+ 2. cd to the tests directory:
+ % cd /usr/tests/sys/pjdfstest
+ 3. Run kyua:
+ % env PJDFSTEST_TEST_PATH=/mnt kyua test
+
+ WARNING: the above method violates the test program isolation algorithm
+ described in kyua(1); as such, $PJDFSTEST_TEST_PATH must be cleaned up after
+ executing the testcases.
+
+ It's highly recommended that $PJDFSTEST_TEST_PATH be pointed to a sandboxed
+ filesystem, e.g. a small UFS-formatted memory disk or ZFS dataset with
+ quotas enabled, so the filesystem can be easily destroyed after the test
+ execution is complete, and the testcases are properly bounded both in terms
+ of time and space.
OpenPOWER on IntegriCloud