Page History

...

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 or combination of distributions, for this reason you can change the tests carried out by indicating in the commit message the changes you require. Test Parameter sessions are  in addition  to the normal tests 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 parameterparameter.

To run additional sessions for your patch, add 'Test-Parameters: ' with space-separated name value pairs to your commit message.

...

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

...

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

...

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 the version node node parameter.

The versions in parenthesis auto-update as new versions are added. For example 1.9 will always point to the highest 1.9.x version. EXA1 will always point to the highest EXA1.x.x version.

...