Difference between revisions of "Test Groups for Patch Testing"

From Lustre Wiki
Jump to navigation Jump to search
(Updated optional and enforced test groups.)
(Moved optional test group to mandatory)
Line 1: Line 1:
When a patch is submitted to Lustre, automated testing is run against a build of Lustre with the submitted patch. Some of these test groups must pass testing, enforced test groups, and others may fail, optional test groups.
+
When a patch is submitted to Lustre, automated testing is run against a build of Lustre with the submitted patch. Some of these test groups must pass testing, enforced test groups, and other, optional, test groups may fail.
 
== Enforced Test Groups ==
 
== Enforced Test Groups ==
There are nine test groups that every patch submitted to Lustre must pass in order for a 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.  
+
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 run in the order below every time they are executed.
+
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.
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 34: Line 34:
 
!review-dne-zfs-part-3
 
!review-dne-zfs-part-3
 
!review-dne-part-4
 
!review-dne-part-4
 +
!review-dne-zfs-part-4
 
|-
 
|-
 
|sanity  
 
|sanity  
Line 41: Line 42:
 
|conf-sanity  
 
|conf-sanity  
 
|conf-sanity  
 
|conf-sanity  
 +
|mmp
 
|mmp  
 
|mmp  
 
|-
 
|-
Line 49: Line 51:
 
|  
 
|  
 
|
 
|
 +
|replay-single
 
|replay-single  
 
|replay-single  
 
|-
 
|-
Line 57: Line 60:
 
|
 
|
 
|
 
|
 +
|sanity-pfl
 
|sanity-pfl
 
|sanity-pfl
 
|-
 
|-
Line 65: Line 69:
 
|
 
|
 
|
 
|
 +
|sanity-flr
 
|sanity-flr
 
|sanity-flr
 
|-
 
|-
Line 73: Line 78:
 
|
 
|
 
|
 
|
 +
|sanity-dom
 
|sanity-dom
 
|sanity-dom
 
|-
 
|-
Line 81: Line 87:
 
|
 
|
 
|
 
|
 +
|sanity-quota
 
|sanity-quota
 
|sanity-quota
 
|-
 
|-
Line 89: Line 96:
 
|
 
|
 
|
 
|
 +
|replay-ost-single
 
|replay-ost-single
 
|replay-ost-single
 
|-
 
|-
Line 97: Line 105:
 
|
 
|
 
|
 
|
 +
|insanity
 
|insanity
 
|insanity
 
|}
 
|}
  
 
== Optional Test Groups ==
 
== Optional Test Groups ==
In addition to the enforced test groups, there are two 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.  
+
In addition to the enforced test groups, there is one optional test group that does 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.  
  
 
The Lustre test suites that compose each optional test group are:
 
The Lustre test suites that compose each optional test group are:
 
{| class="wikitable"
 
{| class="wikitable"
 
! style="text-align:left;" |review-ldiskfs-arm
 
! style="text-align:left;" |review-ldiskfs-arm
!review-dne-zfs-part-4
 
 
|-
 
|-
 
|sanity
 
|sanity
|mmp
 
 
|-
 
|-
 
|lnet-selftest
 
|lnet-selftest
|replay-single
 
 
|-
 
|-
|
 
|sanity-pfl
 
|-
 
|
 
|sanity-flr
 
|-
 
|
 
|sanity-dom
 
|-
 
|
 
|sanity-quota
 
|-
 
|
 
|replay-ost-single
 
|-
 
|
 
|insanity
 
 
|}
 
|}

Revision as of 09:44, 7 March 2019

When a patch is submitted to Lustre, automated testing is run against a build of Lustre with the submitted patch. 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.

review-ldiskfs review-zfs
sanity sanity-quota
lnet-selftest sanity-flr
replay-single
replay-ost-single
insanity

Test groups confgured with DNE; all tests run with 2 MDSs with 2 MDTs each.

review-dne-part-1 review-dne-zfs-part-1 review-dne-part-2 review-dne-zfs-part-2 review-dne-part-3 review-dne-zfs-part-3 review-dne-part-4 review-dne-zfs-part-4
sanity sanity runtests runtests conf-sanity conf-sanity mmp mmp
sanityn sanityn ost-pools ost-pools replay-single replay-single
recovery-small recovery-small sanity-hsm sanity-hsm sanity-pfl sanity-pfl
lustre-rsync-test lustre-rsync-test sanity-scrub sanity-scrub sanity-flr sanity-flr
sanity-lfsck sanity-lfsck sanity-dom sanity-dom
sanity-sec sanity-sec sanity-quota sanity-quota
mds-survey mds-survey replay-ost-single replay-ost-single
large-scale large-scale insanity insanity

Optional Test Groups

In addition to the enforced test groups, there is one optional test group that does 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.

The Lustre test suites that compose each optional test group are:

review-ldiskfs-arm
sanity
lnet-selftest