Versions Compared

Old Version 128

changes.mady.by.user Charlie Olmstead

Saved on

compared with

New Version Current

changes.mady.by.user Andreas Dilger

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: remove mention of liblustre that got into example text?

Table of Contents

Introduction

There may be times that you wish to influence the building and testing carried out on your change. You might for example be fixing an issue that affects a particular distribution, CPU architecture, interoperability with a particular Lustre version, or fails only intermittently and needs multiple test runs to confirm it is fixed.  To address these needs, you can change or add the tests carried out by indicating in the commit message the changes you require. Test-Parameter sessions are normally in addition to the normal test sessions 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 just to try something), it is also possible to submit a patch with the  fortestonly parameter.

...

Code Block
themeMidnight
Test-Parameters: ostcount=2 clients=1 ostsizegb=2 mdssizegb=2 env=SLOW=yes \
                 testlist=sanity,liblustresanityn

A single test can be skipped like this one:

Code Block
themeMidnight
Test-Parameters: testlist=hot-pools env=EXCEPT=75c

which will skip that subtest in the current script, or if multiple test scripts are running then:

Code Block
themeMidnight
Test-Parameters: trivial testlist=hot-pools env=HOT_POOLS_EXCEPT=75c

Quotations can be used when spaces are necessary in a value:

...

The test parameter sessions can be influenced in many ways, see the the  General Parameters and Node Parameters sections below for all of the options.

...

Anchor
build_parameters
build_parameters

Build Parameters

Below are build parameters read by Jenkins, and the Lustre Janitor.

...

Panel
titleignore | flag

Signals to all components the patch should be completely ignored. Jenkins will not build the patch (the status will be FAILURE) and as a result it will not be tested by Autotest or the Lustre Janitor. Your patch will not receive a +/- 1 from Maloo.

Code Block
themeMidnight
Test-Parameters: ignore

...

Panel

...

titleBuild-Parameters:

The Build-Parameters:  directive can limit the architecture/distribution combinations that will be built for a specific patch to only the specified list.  This can be useful in some cases where a large number of patches will be pushed in a series, or when doing bisection testing to isolate a failure to a specific patch.  Note, however, that this only filters the arch/disto combinations from what would normally be built, it cannot add arch/distro combinations that would not otherwise be built for a branch.  Also note that there is not (currently) any coordination between the arch/distro combination that is built and what is tested, so this may also require corresponding "Test-Parameters: ... distro=XXXX arch=YYYY" directives to align the test sessions with the subset of packages being built, including the trivial test sessions that are always run, or use fortestonly to restrict test sessions to only those that are specified.  Use with caution.

Supported keywords are arch and distro that affect both the client and server, or clientarch/clientdistro and serverarch/serverdistro to specify only the client and server builds (one set per line).

Code Block
themeMidnight
Build-Parameters: clientdistro=el9.4 clientarch=aarch64
Build-Parameters: distro=el9.5 arch=x86_64
Build-Parameters: clientdistro=el8.10 arch=x86_64
Test-Parameters: fortestonly
Test-Parameters: kerberos=true testlist=sanity-krb5 clientdistro=el8.10 serverdistro=el9.5
Test-Parameters: kerberos=true testlist=sanity-krb5 clientdistro=el9.4 clientarch=aarch64 serverdistro=el9.5
Test-Parameters: kerberos=true testlist=sanity-krb5 clientdistro=el9.5 serverdistro=el9.5




Anchor
general_parameters
general_parameters

General Parameters

Below is the list of general test parameters that can be used to run custom test sessions. These parameters differ from the node_parameters in that these do not need to be specified with a node type prefix.

...

General Parameters

Below is the list of general test parameters that can be used to run custom test sessions. These parameters differ from the node_parameters in that these do not need to be specified with a node type prefix.

For all of the examples below the 'Test-Parameters:' marker has been omitted to simplify the examples.

...

Panel
titleoptional | Boolean

Marks the test session as optional: does not impact the verified value from Maloo and is only run if resources are immediately available.

Valid values: true, false (no value is the same as true)

Code Block
themeMidnight
# markrun aoptional session as optionalwith some experimental settings
optional
# or
optional=true

# mark a session as required - typically not necessary since false is the default
optional=falsetestlist=sanity env=FSNAME=lus12345

Anchor
ostcount
ostcount

Panel
titleostcount | Integer

The number of OSTs per OSS.

Valid values: 1 - 8

Code Block
themeMidnight
# create 8 OSTs per OSS
osscount=2 ostcount=8

# create 4 OSTs per OSS
osscount=4 ostcount=4

...

Anchor
node_parameters
node_parameters

Node Parameters

Node parameters are used to change how specific node types are configured. They must be prefixed with the node type being changed. Valid node types are client, mds, mgs, oss and server. Server is an alias that allows users to modify a value for all server node types (mds, mgs and oss). For example instead of writing

...

Panel
borderStylesolid
titleversion | String

The version of Lustre to use for the specified node type.

Version cannot be specified with job and build.

If a distro is not specified in the test parameters, Autotest will use the highest el version available for the specified version.

Valid values: For a list of valid versions see the Versions section.

Code Block
themeMidnight
# specify patch level versions
clientversion=2.10.3 serverversion=2.11.0

# specify minor versions which uses the highest patch level version
clientversion=2.10 serverversion=2.11

# specify Exascaler tags in the -ddn[0-9] format
clientversion=2.12.2-ddn2 serverversion=2.14.0-ddn23

# specify Exascaler tags in the EXAx.x.x format
clientversion=EXA5.0.1 serverversion=EXA6.0.0

# specify Exascaler tags in the EXAx format which uses the highest minor version
clientversion=EXA5 serverversion=EXA6

Note that in addition to the more commonly used serverversion=  option, it is possible (to a limited extent) to request separate ossversion= and mdsversion= if necessary.


Anchor
tags
tags

Versions

Versions are pointers to job/build combinations and simplify using a specific Lustre version on a test node. Versions can be specified in the test parameters using the version node parameter.

The versions in parenthesis auto-update as new versions are added. For example 1.9 will always point to the highest 1.9.x version. EXA1 will always point to the highest EXA1.x.x version.If there is a version missing, send an email to  charlie@whamcloud.com
-update as new versions are added. For example 1.9 will always point to the highest 1.9.x version. EXA1 will always point to the highest EXA1.x.x version.

If there is a version missing, send an email to  charlie@whamcloud.com

Version

Build

2.7.0 (2.7)

https://build.whamcloud.com/job/lustre-b2_7/29/

2.8.0 (2.8)

https://build.whamcloud.com/job/lustre-b2_8/12/

2.9.0 (2.9)

https://build.whamcloud.com/job/lustre-b2_9/22/

2.10.0

https://build.whamcloud.com/job/lustre-b2_10/5/

2.10.1

Version

Build

2.7.0 (2.7)

https://build.whamcloud.com/job/lustre-b2_710/2930/

2.810.0 (2.8)

https://build.whamcloud.com/job/lustre-b2_810/1252/

2.9.0 (2.9)10.3

https://build.whamcloud.com/job/lustre-b2_910/2269/

2.10.04

https://build.whamcloud.com/job/lustre-b2_10/5116/

2.10.15

https://build.whamcloud.com/job/lustre-b2_10/30136/

2.10.26

https://build.whamcloud.com/job/lustre-b2_10/52152/

2.10.37

https://build.whamcloud.com/job/lustre-b2_10/69168/

2.10.4.8 (2.10)

https://build.whamcloud.com/job/lustre-b2_10/116170/

2.10.511.0 (2.11)

https://build.whamcloud.com/job/lustre-b2_1011/1362/

2.1012.60

https://build.whamcloud.com/job/lustre-b2_1012/1522/

2.1012.71

https://build.whamcloud.com/job/lustre-b2_1012/16813/

2.1012.8 (2.10)

https://build.whamcloud.com/job/lustre-b2_1012/17018/

2.11.0 (2.11)12.3

https://build.whamcloud.com/job/lustre-b2_1112/253/

2.12.04

https://build.whamcloud.com/job/lustre-b2_12/266/

2.12.15

https://build.whamcloud.com/job/lustre-b2_12/1387/

2.12.26

https://build.whamcloud.com/job/lustre-b2_12/18112/

2.12.37

https://build.whamcloud.com/job/lustre-b2_12/53135/

2.12.48

https://build.whamcloud.com/job/lustre-b2_12/66152/

2.12.5.9 (2.12)

https://build.whamcloud.com/job/lustre-b2_12/87164/

2.13.12.60 (2.13)

https://build.whamcloud.com/job/lustre-b2_1213/112/6/

2.14.0 (2.14) 2.12.7

https://build.whamcloud.com/job/lustre-b2_1214/1352/

2.1215.80

https://build.whamcloud.com/job/lustre-b2_1215/15213/

2.12.9 (2.12)15.1

https://build.whamcloud.com/job/lustre-b2_1215/16428/

2.1315.0 (2.13)

https://build.whamcloud.com/job/lustre-b2_1315/648/

2.14.0 (2.14)15.3

https://build.whamcloud.com/job/lustre-b2_1415/265/

2.15.04

https://build.whamcloud.com/job/lustre-b2_15/1381/

2.15.15

https://build.whamcloud.com/job/lustre-b2_15/2894/

2.15.26

https://build.whamcloud.com/job/lustre-b2_15/48100/

2.15.3.7 (2.15)

https://build.whamcloud.com/job/lustre-b2_15/65107/

2.1516.40

https://build.whamcloud.com/job/lustre-b2_1516/812/

2.1516.5 1 (2.1516)

https://build.whamcloud.com/job/lustre-b2_1516/946/

EXAScaler Versions


Anchor
test_groups_section
test_groups_section

Test Groups

Test groups are set lists of Lustre test suites managed by Autotest.

...