Test Groups for Patch Testing

When a patch is submitted to be considered for inclusion in Lustre, automated testing is run against a build of Lustre with the submitted patch. For a patch to land, some of these test groups must pass testing, enforced test groups, and other, optional, test groups may fail.

Enforced Test Groups
There are ten test groups that every patch must pass in order for the patch to be considered for landing. If there is a failure in any one of these test sessions, a patch will not be allowed to land to the Lustre branch. The Lustre test suites that compose each test group are listed in the following table and the test suites in each test group are run in the order below every time they are executed.

All of the following test groups are run in a Lustre environment with DNE configured; all tests run with 2 MDSs with 2 MDTs each.

Optional Test Groups
In addition to the enforced test groups, there are four optional test groups that do not influence if a patch can land. These optional test groups will become enforced test groups for patch landing in the near future and should be reviewed for failures.