Versions Compared

Old Version 53

changes.mady.by.user Charlie Olmstead

Saved on

compared with

New Version 54

changes.mady.by.user Charlie Olmstead

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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

only review-ldiskfs is run

for trivial

for trivial patches (see Autotest Plan for details). 

The Verified

The Verified flag will be set upon successful test completion(s).

 
testgroup
Test group to test with. testgroup can be combined with testlist:

 

Code Block
Test-Parameters: testgroup=review-ldiskfs testlist=sanity-selinux

 

will run the review-ldiskfs test group and the sanity-selinux test suite
review, regression, full, review-ldiskfs, review-dne-part-1, review-dne-part-2, review-zfs-part-1, review-zfs-part-2, etc.
testlistComma 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.
fortestonlyPatch 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. 
forbuildonlyPatch will be built by Jenkins, but no testing will be done. The Verified flag will not be set by Maloo for landing. 
clientcountNumber of clients to use2-4
mdscountNumber of MDSs to test against1-4
mdtcountNumber of MDTs to test against1-4
osscountNumber of OSTs to test against1-4
ostcountNumber of OSTs per OSS to test against1-4
clientprofileCobbler profile to use for clientstest
mdsprofile,ossprofileCobbler profile to use for serverstest
clientdistroDistribution to use for clientsel6, el7, sles11, sles11sp2, sles12sp3, ubuntu1604, etc.
mdsdistro, ossdistroDistribution to use for serversel6, el7, sles11, sles11sp2, sles12sp3, etc.
clientarchArchitecture to use for clientsi686, x86_64, ppc64
mdsarch, ossarchArchitecture to use for serversi686, x86_64
clientjobJenkins 'job' to fetch from for the clients under testAny valid Jenkins job, such as lustre-reviews, lustre-master, etc.
clientbuildnoJenkins build number to fetch for the clients under testAny valid Jenkins buildno for clientjob
mdsjob, ossjobJenkins 'job' to fetch from for the servers under testAny valid Jenkins job, such as lustre-reviews, lustre-master, etc.
serverbuildnoJenkins build number to fetch for the servers under testAny valid Jenkins build number for mdsjob or ossjob
nettypesNetwork types to use as a comma separated arraytcp, o2ib
ostsizegbSize of OSTs in GB. Note this is a max size and will be limited by the disk available>0
mdssizegbSize of MDS in GB. Note this is a max size and will be limited by the disk available>0
mdtfilesystemtypeFile system to use for MDTs and MGSzfs, ldiskfs
ostfilesystemtypeFile system to use for OSTszfs, ldiskfs
clientibstackIB stack to use on the client.inkernel, ofa
serveribstackIB stack to use on the server.inkernel, ofa
envdefinitions
Comma separated environment definitions passed to the environment.

 

Panel
Be very careful setting environment variables directly (for example OSTFSTYPE=zfs) because autotest creates a config file based on the environment it builds, and if you ask for something at odds with autotest's expectations you will see failure instead of success.  In this case, for example, you should use the filesystemtype the filesystemtype keyword described on this page. Autotest will then create the appropriate environment variables, the same is true for other things like ostcount instead of OSTCOUNTof OSTCOUNT, ostsizegb instead of OSTSIZEof OSTSIZE, etc. Only use the envdefinitions the envdefinitions variable when a direct variable is not listed here.
ONLY=26,EXCEPT=22
alwaysuploadlogsBy default autotest will upload logs on passing tests. This will force it do upload logs. This option is no longer necessary. 
failoverSetup cluster in failover configuration 
iscsiUse iSCSI for failover testing0, 1
combinedmdsmgsUse 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
standalonemgsSetup 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=3true, 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.

...