Page History
...
| Code Block |
|---|
Test-Parameters: ostcount=2 clients=1 ostsizegb=2 mdssizegb=2 envdefinitions=SLOW=yes \ testlist=sanity,liblustre |
Quotations can be used when spaces are necessary in a value:
| Code Block |
|---|
Test-Parameters: testlist=sanity envdefinitions=SANITY_EXCEPT="101g 102i" |
testlist=
Multiple tests are separated by a comma, and can be specified multiple times. This is useful if a patch is fixing a problem that is only hit intermittently by a test script, and multiple tests need to be run in order to gain more confidence that the problem is actually fixed. For example, if replay-dual was failing 1/3 of test runs, it would be useful to run it at least twice the average number of times needed to hit a failure to have some reasonable expectation that the bug is fixed. With just a single test run, there would be a 66% chance a single test would pass even if the bug was not fixed, but only about a 9% chance (2/36 = 64/729) that 6 separate tests would pass without the bug being fixed. If the number of tests needed is more than about 3-4 (depending on how long each test runs), then multiple Test-Parameters: lines should be used, so that the tests are run in separate sessions (usually in parallel) rather than in series.
...
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). | ||||
| testgroup | Test group to test with. testgroup can be combined with testlist:
| review, regression, full, review-ldiskfs, review-dne-part-1, review-dne-part-2, review-zfs-part-1, review-zfs-part-2, etc. | |||
| testlist | Comma separated list of test names to run in place of a standard test group. testlist can be combined with testgroup. See testgroup for an example. | sanity,sanityn, conf-sanity, mmp, replay-single, replay-dual, lnet-selftest, etc. | |||
| fortestonly | 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 testlist= parameter. The Verified flag will not be set by Maloo for landing. | ||||
| forbuildonly | Patch will be built by Jenkins, but no testing will be done. The Verified flag will not be set by Maloo for landing. | ||||
| clientcount | Number of clients to use | 2-4 | |||
| mdscount | Number of MDSs to test against | 1-4 | |||
| mdtcount | Number of MDTs to test against | 1-4 | |||
| osscount | Number of OSTs to test against | 1-4 | |||
| ostcount | Number of OSTs per OSS to test against | 1-4 | |||
| clientprofile | Cobbler profile to use for clients | test | |||
| mdsprofile,ossprofile | Cobbler profile to use for servers | test | |||
| clientdistro | Distribution to use for clients | el7, sles11, sles11sp2, sles12sp3, ubuntu1604, etc. | |||
| mdsdistro, ossdistro | Distribution to use for servers | el7, sles11, sles11sp2, sles12sp3, etc. | |||
| clientarch | Architecture to use for clients | x86_64, ppc64 | |||
| mdsarch, ossarch | Architecture to use for servers | x86_64 | |||
| clientjob | Jenkins 'job' to fetch from for the clients under test | Any valid Jenkins job, such as lustre-reviews, lustre-master, etc. | |||
| clientbuildno | Jenkins build number to fetch for the clients under test | Any valid Jenkins buildno for clientjob | |||
| mdsjob, ossjob | Jenkins 'job' to fetch from for the servers under test | Any valid Jenkins job, such as lustre-reviews, lustre-master, etc. | |||
| serverbuildno | Jenkins build number to fetch for the servers under test | Any valid Jenkins build number for mdsjob or ossjob | |||
| nettypes | Network types to use as a comma separated array | tcp, o2ib | |||
| ostsizegb | Size of OSTs in GB. Note this is a max size and will be limited by the disk available | >0 | |||
| mdssizegb | Size of MDS in GB. Note this is a max size and will be limited by the disk available | >0 | |||
| mdtfilesystemtype | File system to use for MDTs and MGS | zfs, ldiskfs | |||
| ostfilesystemtype | File system to use for OSTs | zfs, ldiskfs | |||
| clientibstack | IB stack to use on the client. | inkernel, ofa | |||
| serveribstack | IB stack to use on the server. | inkernel, ofa | |||
| envdefinitions | Comma separated environment definitions passed to the environment.
| ONLY=26,EXCEPT=22 | |||
| 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 | |||
| standalonemgs | Setup the MGS on a separate test node. The MGS will be setup with the same parameters as the MDS but can be overridden e.g. mgssizegb=2 mdssizegb=3 | true, false |
...
Overview
Content Tools