"SfR Fresh" - the SfR Freeware/Shareware Archive

Member "pvfs-2.7.1/test/automated/README.tests" of archive pvfs-2.7.1.tar.gz:

As a special service "SfR Fresh" has tried to format the requested source page into HTML format using source code syntax highlighting with prefixed line numbers. Alternatively you can here view or download the uninterpreted source code file. That can be also achieved for any archive member file by clicking within an archive contents listing on the first character of the file(path) respectively on the according byte size field. 
    1 #
    2 # $Date: 2006/09/13 20:23:03 $
    3 #
    4 # A brief description of the contents of the test/automated directory
    5 
    6 
    7 From time to time we (pvfs2 developers) make an effort to thouroughly
    8 test pvfs2.  We really do think it's important... it just ends up taking
    9 a back seat to lots of other important items.   
   10 
   11 CURRENT APPROACH:
   12 
   13   It would be hard to describe this as "minimally invasive".  We want to
   14   test the VFS interface in addition to the libpvfs and mpi-io
   15   interfaces, so we need significant modifications to the host machine.
   16   At MCS, we have 'gil' and 'lain', two "red" machines (machines on
   17   which we have root acces and no support from our system
   18   adminitrators).  
   19 
   20   The scripts require occaional root access, so it's best to set up sudo
   21   with a NOPASSWD entry (i.e. a line like "robl    ALL=NOPASSWD: ALL" in
   22   /etc/sudoers).  
   23 
   24   The main driver is 'testscrpt.sh' (name subject to change).  It
   25   builds pvfs2, starts up the servers, loads the kernel module, and
   26   starts pvfs2-client and pvfs2-client-core.   The script needs a few
   27   variables set:
   28 
   29     PVFS2_DEST:       staging location for checking out, building, logging
   30     PVFS2_MOUNTPOINT: where we mount pvfs2
   31     EXTRA_TESTS:      directory where more sophisticated benchmarks (like
   32                       bonnie, iozone, ior, etc) live
   33 
   34   Then it proceeds to run every executable file in 'sysint-tests.d',
   35   'vfs-tests.d' and 'mpiio-tests.d' These files are simple little shell
   36   scripts that do something to exercise pvfs2.  
   37 
   38   Sam set up a tinderbox on lain.mcs.anl.gov, and wrote
   39   tinder-pvfs2-status to make it easy for scripts to lob bits at it.   A
   40   couple things that tripped me up when I first started using it:
   41 
   42   - The states are enumerated in 'BuildStatus.pm' in the tinderbox
   43     directory.  
   44   - there seems to be a 6 minute interval where if you start a new run
   45     you'll overwrite the old run
   46 
   47 On a Cluster:
   48   The common way to deploy PVFS2 on a cluster is through our pav
   49   scripts.  Thus, we need a pav config file, specified by the PAV_CONFIG
   50   variable.  We also want to run the usual battery of tests
   51 
   52 OLDER APPROACHES:
   53 
   54 These files aren't used anymore but might provide someone with some
   55 useful ideas on how to script up a benchmark and interact with PBS.  If
   56 anybody wants to document them, feel free to elaborate on this section.
   57 
   58   bonnie++.sh
   59   CONFIG.template
   60   kmod_ctrl.sh
   61   PAVCONFIG.template
   62   pvfs2tests.py
   63   run-cron-adenine.sh
   64   run-cron-heroin.sh
   65   run-test-adenine.sh
   66   simple.sh
   67   single-node-kernel-test.sh
   68   SUBMIT.pbs.template
   69 
   70 # vim: tw=72