andy/glusterfs
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
glusterfs/tests/README.md
Harshavardhana 2ec6ea43f2 build: make GLUSTERD_WORKDIR rely on localstatedir 
- Break-way from '/var/lib/glusterd' hard-coded previously,
  instead rely on 'configure' value from 'localstatedir'
- Provide 's/lib/db' as default working directory for gluster
  management daemon for BSD and Darwin based installations
- loff_t is really off_t on Darwin
- fix-off the warnings generated by clang on FreeBSD/Darwin
- Now 'tests/*' use GLUSTERD_WORKDIR a common variable for all
  platforms.
- Define proper environment for running tests, define correct PATH
  and LD_LIBRARY_PATH when running tests, so that the desired version
  of glusterfs is used, regardless where it is installed.
  (Thanks to manu@netbsd.org for this additional work)

Change-Id: I2339a0d9275de5939ccad3e52b535598064a35e7
BUG: 1111774
Signed-off-by: Harshavardhana <harsha@harshavardhana.net>
Signed-off-by: Emmanuel Dreyfus <manu@netbsd.org>
Reviewed-on: http://review.gluster.org/8246
Tested-by: Gluster Build System <jenkins@build.gluster.com>
2014-08-07 01:17:29 -07:00

1.5 KiB
Raw Blame History

Regression tests framework for GlusterFS

Prereq

  • Build and install the version of glusterfs with your changes. Make sure the installed version is accessible from $PATH.

How-To

  • To mount glusterfs, NEVER use 'mount -t glusterfs', instead use 'glusterfs -s ' method. This is because with the patch build setup doesnot install the /sbin/mount.glusterfs necessary, where as the glusterfs binary will be accessible with $PATH, and will pick the right version.
  • (optional) Set environment variables to specify location of export directories and mount points. Unless you have special requirements, the defaults should just work. The variables themselves can be found at the top of tests/include.rc. All of them can be overriden with environment variables.

Usage

  • Execute /usr/share/glusterfs/run-tests.sh as root.

  • If you want to run individual tests located in /usr/share/glusterfs/tests as opposed to the full test-suite, invoke it as /usr/share/glusterfs/run-tests.sh [pattern]*, where pattern can be:

    • the trailing parts of the full path of a test, e.g. tests/basic/mount.t
    • the name of a file or directory, e.g self-heal.t or basic/
    • bug number, which will match against numbered bugs in the tests/bugs/ directory.
    • a glob pattern (see man 7 glob for mor info on globs)

  • If some test cases fail, report to GlusterFS community at gluster-devel@gluster.org.

Reminder

  • BE WARNED THAT THE TEST CASES DELETE GLUSTERD_WORKDIR * !!!