Versions Compared

Key

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

...

To do this place the following comments with space-separated name value pairs in your commit message:

...

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

Multiple tests are separated by a comma, and can be specified multiple times:

Code Block

Test-Parameters: ostcount=2 clients=1 ostsizegb=2 \
mdssizegb=2 \
envdefinitions=SLOW=yes \
testlist=sanity,liblustrereplay-dual,replay-single,replay-dual,replay-single,replay-single,replay-dual

fortestonly

Test-Parameters supplied with a normal commit 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), it is also possible to submit a patch with the fortestonly parameter.

...

Name

Description

Valid Values

fortestonly

Commit is not indended for landing

 

ostcount

Number of OSTs to test against

1..10

clientprofile

Cobbler profile to use for clients

test

serverprofile

Cobbler profile to use for servers

test

clientdistro

Distribution to use for clients

el5, el6, sl11, ub10

serverdistro

Distribution to use for servers

el5, el6, sl11

clientarch

Architecture to use for clients

i686, x86_64, ppc

serverarch

Architecture to use for servers

i686, x86_64

clientjob

Jenkins 'job' to fetch from for the clients under test

Any valid jenkins job

clientbuildno

Jenkins buildno to fetch for the clients under test

Any valid build no for clientjob

serverjob

Jenkins 'job' to fetch from for the servers under test

Any valid jenkins job

serverbuildno

Jenkins buildno to fetch for the servers under test

Any valid build for serverjob

nettype

Network type to use

tcp, o2ib

clientcount

Number of clients to use

2-4

no_virtualization

Set True if testing must not be virtualized

true

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

filesystemtype

File system to use for OST and MDS

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.

AA=BB,CC=DD etc.

testgroup

Test group to test with

review, regression, quick, full

testlist

Comma separated list of test names to run in place of a standard test group . The same test name can be given multiple times to run that test repeatedly.

sanity,conf_sanity,mmp etc

...