Page History
...
The trivial keyword can be used to reduce the testing time (both wall-clock time as well as total test system hours) for patches that do not affect code functionality, such as changes to whitespace, comments, man pages, and test scripts (in conjunction with the testlist keyword to ensure the modified test script is run if it isn't already). Patches marked with trivial in the Test-Parameters: list will only will run the review-ldiskfs test session , which instead of the regular tests, so it currently runs only sanity and lnet-selftest to ensure basic functionality. If changes are only being made to a test script outside of those already run by default, an additional testlist=<test-script(s)> keyword should be added with a comma-separated list of modified tests to ensure they are run to validate the changes. The trivial keyword will reduce the test completion time from approximately 10h elapsed and 30h of total test system time to approximately 3h elapsed/system time. This saves test system resources that may be better spent on other patches.
Permissible Test-Parameters: options
Name | Description | Valid Values | ||
|---|---|---|---|---|
trivial | Patch contains only whitespace, comment, man page, or test script (with additional testlist=) updates and requires minimal testing. Currently, only review-ldiskfs is run for trivial patches (see Autotest Plan for details). The Verified flag will be set upon successful test completion(s). | |||
| Test group to test with |
| ||
| Comma separated list of test names to run in place of a standard test group |
| ||
| Patch will be built by Jenkins. A single review test session will be run by default, unless another specific test list is specified using the |
| ||
forbuildonly | Patch will be built by Jenkins, but no testing will be done. The Verified flag will not be set by Maloo for landing. | |||
| Number of clients to use | 2-4 | ||
| Number of MDSs to test against | 1-4 | ||
| Number of MDTs to test against | 1-4 | ||
| Number of OSTs to test against | 1-4 | ||
| Number of OSTs per OSS to test against | 1-4 | ||
| Cobbler profile to use for clients | test | ||
| Cobbler profile to use for servers | test | ||
| Distribution to use for clients |
| ||
| Distribution to use for servers |
| ||
| Architecture to use for clients |
| ||
| Architecture to use for servers |
| ||
| Jenkins 'job' to fetch from for the clients under test | Any valid Jenkins job, such as | ||
| Jenkins build number to fetch for the clients under test | Any valid Jenkins buildno for | ||
| Jenkins 'job' to fetch from for the servers under test | Any valid Jenkins job, such as | ||
| Jenkins build number to fetch for the servers under test | Any valid Jenkins build number for | ||
| Network types to use as a comma separated array |
| ||
| Size of OSTs in GB. Note this is a max size and will be limited by the disk available | >0 | ||
| Size of MDS in GB. Note this is a max size and will be limited by the disk available | >0 | ||
| File system to use for MDTs and MGS |
| ||
| File system to use for OSTs |
| ||
| IB stack to use on the client. |
| ||
| IB stack to use on the server. |
| ||
| Comma separated environment definitions passed to the environment.
|
| ||
alwaysuploadlogs | By default autotest will upload logs on passing tests. This will force it do upload logs. This option is no longer necessary. | |||
failover | Setup cluster in failover configuration | |||
iscsi | Use iSCSI for failover testing | 0, 1 | ||
combinedmdsmgs | Use a combined server storage target for the MDS and MGS or use separate targets for the MDS and MGS. If false, the MGS and MDS will be on the same node, but the MDT and MGT will be separate storage targets. Default value is true; a combined storage target. | true, false |
You do not need to specify all the values only those values important for your requirements, the test system will use your request to alter a regular test. Also to ensure that you all reviews are fully tested to a known standard. The test system will run a regular, unmodified test set as well as the special request.
...
Overview
Content Tools