Page History

...

$ /usr/lib64/lustre/tests/auster -h
Usage auster [options]  suite [suite options] [suite [suite options]]
Run Lustre regression tests suites.
      -c CONFIG Test environment config file
      -d LOGDIR Top level directory for logs
      -D FULLLOGDIR Full directory for logs
      -f STR    Config name (cfg/<name>.sh)
      -g GROUP  Test group file (Overrides tests listed on command line)
      -S TESTSUITE First test suite to run allows for restarts
      -H        Honor the EXCEPT and ALWAYS_EXCEPT list when --only is used
      -i N      Repeat tests N times (default 1). A new directory
                will be created under LOGDIR for each iteration.
      -k        Don't stop when subtests fail
      -R        Remount lustre between tests
      -r        Reformat (during initial configuration if needed)
      -s        SLOW=yes
      -v        Verbose mode
      -l        Send logs to the Maloo database after run
                  (can be done later by running maloo_upload.sh)
      -h        This help.

Suite options
These are suite specific options that can be specified after each suite on
the command line.
   suite-name  [options]
      --only LIST         Run only specific list of subtests
      --except LIST       Skip list of subtests
      --start-at SUBTEST  Start testing from subtest
      --stop-at SUBTEST   Stop testing at subtest
      --time-limit LIMIT  Don't allow this suite to run longer
                          than LIMT seconds. [UNIMPLEMENTED]


Example usage:
Run all of sanity and all of replay-single except for 70b with SLOW=y using
the default "local" configuration.

  auster -s sanity replay-single --except 70b

Run all tests in the regression group 5 times using large config.

  auster -f large -g test-groups/regression -i 5

...

# cd /usr/lib64/lustre/tests
edit cfg/testfs.sh
Minimum required variables: mds_HOST, ost_HOST, PDSH, MDSDEV1, OSTCOUNT, OSTDEV#, MDS_MOUNT_OPTS, OST_MOUNT_OPTS


See Lustre Test Tools Environment Variable for more infomationinformation
Make sure partitions on the disks are setup
If using real devices, make sure to set MDS_MOUNT_OPTS, OST_MOUNT_OPTS = ""
If there is more than one clients set RCLIENTS=<list of remote clients>


# ./auster -rvf testfs runtests (or any other test suite)

...

Many Lustre test suites have subtests that test the same feature or functionality. These tests are numbered with an integer followed by a letter. If a test suite has tests with the same number with different letters appended, then you can run all tests with the same number, all letters, by specifying only the number in the "--only" list of tests.

...

will run abc.sh tests 2a, 2b, 2c, 2d, and 2e.

Using By default, using the "--only" flag overrides the ALWAYS_EXCEPT list in the test suite script and will execute a test in the "--only" list even if the same test is on the ALWAYS_EXCEPT list. For example, assume abc.sh test suite has ALWAYS_EXCEPT=”2c 3 4” defined, running

...

will run abc.sh tests 2a, 2b, 2c, 2d, 2e, and 3 even though test 2c and test 3 are on the ALWAYS_EXCEPT list.

If you specify a test that does not exist in the "--only" list of tests to run, no warning or error messages are printed. For example, runningAuster provides a way to override this default behavior of ignoring the ALWAYS_EXCEPT list when using --only by using the '-H' flag. 

./auster -H abc --only "2 v4d3"

will not complain that test 4d does not exist.run abc.sh tests 2a, 2b, 2d and 2e only. The ALWAYS_EXCEPT list is honored and tests 2c and 3 are skipped.

If you specify a test that does not exist in the "--only" list of tests to run, no warning or error messages are printed. For example, running

./auster abc --only v4d

will not complain that test 4d does not exist.

Run a Range of Tests with auster

Range of tests using --only

If you want to run a range of tests, you can use the test suite flag "--only”.

./auster abc --only "11-14"
./auster abc --only 11-14

will run abc.sh tests 11, 12, 13, and 14.

The test number at the beginning and/or end of the range does not have to exist in the test suite; all tests in a range that exist are run. For example,

./auster abc --only 10-15

will run abc.sh tests 11, 12, 13, and 14.

Spaces between the hyphen are not allowed and will give an error and will not run any tests.

./auster abc --only “10 – 15”

will run no tests.

More than one range can be specified. The ranges will be combined and tests will be run in numerical order.

./auster abc --only "11-14 3-4"
./auster abc --only "11-14,3-4"
./auster abc --only 11-14,3-4

will run abc.sh tests in the order of 3, 4, 11, 12, 13, and 14.

Ranges can overlap and each test will only be run once even if it is specified in more than one range.

./auster abc --only "11-13,12-14"

will run abc.sh tests 11, 12, 13, and 14.

If the –only flag is used more than once for the same test suite, only the tests specified in the range of the last –only flag will be run.

./auster abc --only 3-4 --only 12-14

will run abc.sh tests 12, 13, and 14. Tests 3 and 4 will not be run.

If a test suite has tests with the same number with letters appended, then all tests with the same number all letters will be run if the test number falls into a range.

./auster abc --only 6-10

will run abc.sh tests 6, 7a 7b, and 7c.

Using a range with the --only flag overrides the ALWAYS_EXCEPT list in the test suite script and will execute a test in the –only list even if the same test is on the ALWAYS_EXCEPT list. For example, assume abc.sh test suite has ALWAYS_EXCEPT=”2c 3 4” defined, running

./auster abc --only 3-5

will run abc.sh tests 3, 4, 5a, and 5b even though tests 3 and 4 are on the ALWAYS_EXCEPT list.

The --only flag does not allow a range to start with a subtest, a number followed by a letter, and does not allow a range to end with a subtest. All of the following will get an error “seq: invalid floating point argument: 2d” or “seq: invalid floating point argument: 5d” and no tests will be run. The following are NOT supported

./auster abc --only “2d-5a”
./auster abc --only “2d-4”
./auster abc --only “3-5d”

Range of tests using --start-at and --stop-at

The per test suite options --start-at and --stop-at currently do not change what tests are run and should not be used. 

./auster abc --start-at 3 --stop-at 6

will run all tests in abc.sh ignoring the --start-at and --stop-at flags.

Using the tests individually do not control starting or stopping of executing tests and should not be used individually. The following do notchange what tests are run and should NOT be used

./auster abc --start-at 3
./auster abc --stop-at 6

Exclude Individual Tests with auster

If you do not want to run a test or a small number of tests, auster provides the --except flag to exclude tests from being run.

 ./auster -k -v abc --except 3

will run all tests in abc.sh except for test 3. 

If a test has subtests, the --except flag can be used to skip all subtests just by specifying the test number.

./auster -k -v abc --except 1

will run all tests in test suite abc.sh except for test 1 and will not run all subtests of 1. Thus, 1a, 1b, 1c, 1d, and 1e will not be run, but all other tests will executed. Also, tests listed on the ALWAYS_EXCEPT list are also skipped.

Skipping individual subtests is also supported.

./auster -k -v abc --except 1b

will run all tests in test suite abc.sh except for test 1b. Thus, 1a, 1c, 1d, and 1e will be run along with all other tests  greater than 1 in abc.sh.

 ./auster -k -v abc --except 1,2,3,4,5,6,7

will skip tests 1 through 7 and all sub tests.

Exclude Ranges of Tests with auster

Specifying a range of tests to exclude does not work and no tests will be executed. The following does NOT work

./auster -k -v abc --except 1-7
./auster -k -v abc --except “1-7”