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: n=v x=y

To cater for multiple requirements we allow for lists of requirements, with each entry being a separate test:

Code Block

Test-Parameters: x=y c=e
Test-Parameters: e=z r=e

Long lists can be catered for by escaping the carriage return:

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=replay-dual,replay-single,replay-dual,replay-single,replay-single,replay-dual

...

Name

Description

Valid Values

fortestonly

Commit is not indended for landing

 

ostcount

Number of OSTs to test against

1..2000

mdscount

Number of MDSs to test against

1

mdtcount

Number of MDTs to test against

1..10

osscount

Number of OSTs to test against

1..2

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

nettypes

Network types to use as a comma separated array

tcp, o2ib

clientcount

Number of clients to use

2-4

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

mdsfilesystemtype

File system to use for MDSs

zfs, ldiskfs

mdtfilesystemtype

File system to use for MDTs

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.

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 autotests expectations you will see failure not success.
In this case for example you should use the filesystemtype described on this page.
Autotest will then create the appropriate environment variables, the same is true for
other things like ost numbers, ost size etc etc. Only use the envdefinitions variable
when a direct variable is not present

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

sanity,conf_sanity,mmp etc

...

Here is an example:

Code Block

LU-1234 recovery: handle swabbing during recover

Handle byte swabbing of requests properly during recovery.  There were
problems with the handling of replayed creates that sent the requests
with client-endian order but a little-endian LOV EA.

Test-Parameters: clientdistro=el5 clientarch=ppc serverarch=x86_64 \
                 ostcount=10 nettype=tcp teststestlist=conf-sanity,replay-single
Test-Parameters: clientdistro=sl11 serverdistro=rh6 clientarch=ppc \
                 nettype=o2ib teststestlist=conf-sanity,replay-single

Signed-off-by: Random J Developer <random@developer.example.org>
Change-Id: Ica9ed1612eab0c4673dee088f8b441d806c64932

...

Test a review for failover

Code Block

Test-Requirements: fortestonly envdefinitions="SLOW=yes" clientcount=4 osscount=2 mdscount=2 austeroptions=-R failover=true useiscsi=true testgroup=failover