Introduction

There may be times that you wish to influence the building and testing carried out on your change. You might for example be fixing an issue that affects a particular distribution, CPU architecture, interoperability with a particular Lustre version, or fails only intermittently and needs multiple test runs to confirm it is fixed.  To address these needs, you can change or add the tests carried out by indicating in the commit message the changes you require. Test-Parameter sessions are normally in addition to the normal test sessions that would be run against a patch. This allows a patch with specific or unusual testing requirements to ensure that sufficient additional testing is run to gain confidence in the change being made. For patches that are of an experimental nature (i.e. developer is not sure of functionality, or only wants a limited set of tests to be run just to try something), it is also possible to submit a patch with the  fortestonly parameter.

...

Test-Parameters: ostcount=2 clients=1 ostsizegb=2 mdssizegb=2 env=SLOW=yes \
                 testlist=sanity,liblustre

A single test can be skipped like this one:

Test-Parameters: testlist=hot-pools env=EXCEPT=75c

which will skip that subtest in the current script, or if multiple test scripts are running then:

Test-Parameters: trivial testlist=hot-pools env=HOT_POOLS_EXCEPT=75c

Quotations can be used when spaces are necessary in a value:

...

The test parameter sessions can be influenced in many ways, see the the  General Parameters and Node Parameters sections below for all of the options.

...

Build Parameters

Below are build parameters read by Jenkins, and the Lustre Janitor.

...

General Parameters

Below is the list of general test parameters that can be used to run custom test sessions. These parameters differ from the node_parameters in that these do not need to be specified with a node type prefix.

...

Node Parameters

Node parameters are used to change how specific node types are configured. They must be prefixed with the node type being changed. Valid node types are client, mds, mgs, oss and server. Server is an alias that allows users to modify a value for all server node types (mds, mgs and oss). For example instead of writing

...

# specify patch level versions
clientversion=2.10.3 serverversion=2.11.0

# specify minor versions which uses the highest patch level version
clientversion=2.10 serverversion=2.11

# specify Exascaler tags in the -ddn[0-9] format
clientversion=2.12.2-ddn2 serverversion=2.14.0-ddn23

# specify Exascaler tags in the EXAx.x.x format
clientversion=EXA5.0.1 serverversion=EXA6.0.0

# specify Exascaler tags in the EXAx format which uses the highest minor version
clientversion=EXA5 serverversion=EXA6

Versions

Versions are pointers to job/build combinations and simplify using a specific Lustre version on a test node. Versions can be specified in the test parameters using the version node parameter.

...

Anchor
test_groups_section test_groups_section

Test Groups

Test groups are set lists of Lustre test suites managed by Autotest.

...