Testing: Difference between revisions

From Lustre Wiki
Jump to navigation Jump to search
(Created page with "{| class="wikitable" |+Lustre Test Suites |- |runtests |Simple basic regression test that verifies data persistence across write, unmount, and remount. This is one of the few...")
 
(remove broken link)
(22 intermediate revisions by 5 users not shown)
Line 1: Line 1:
{| class="wikitable"
* [[Testing HOWTO | Run Lustre Tests HOWTO]]
|+Lustre Test Suites
* [[Test Descriptions | Test Framework and Descriptions of Unit, Regression, and Feature Tests]]
|-
* [[Testing Setup To Induce Race Conditions | Testing setup to induce otherwise hard to hit race conditions]]
|runtests
* [[Test Groups for Patch Testing | Test Groups for Patch Testing]]
|Simple basic regression test that verifies data persistence across write, unmount, and remount. This is one of the few tests that verifies data integrity across a full filesystem shutdown and remount, unlike many tests which at most only verify the existence/size of files. (Source [https://wiki.hpdd.intel.com/display/PUB/Auster HPDD Wiki Auster])
----
|-
Whamcloud's testing results database for patches: [https://testing.whamcloud.com/ Maloo]
|sanity
 
|A set of regression tests that verify operation under normal operating conditions. This tests a large number of unusual operations that have previously caused functional or data correctness issues with Lustre. Some of the tests are Lustre specific, and hook into the Lustre fault injection framework using the "lctl set_param fail_loc=X" command to activate triggers in the code to simulate unusual operating conditions that would otherwise be difficult or impossible to simulate. (Source [https://wiki.hpdd.intel.com/display/PUB/Auster HPDD Wiki Auster])
Whamcloud Wiki pages related to testing:
|-
* [https://wiki.whamcloud.com/display/PUB/Testing+a+Lustre+filesystem Testing a Lustre filesystem]
|fsx
* [https://wiki.whamcloud.com/display/PUB/Lustre+Test+Tools+Environment+Variables Lustre Test Tools Environment Variables]
|The file system exerciser was developed outside of Lustre and is intended to stress test unusual IO and file operations. It does buffered and mmap reads and writes with random size and offset, truncate, open, close on a file. It verifies data integrity after each step. A lustre-developed extension allows fsx to run against multiple mountpoints to verify distributed IO operation correctness. (Source [https://wiki.hpdd.intel.com/display/PUB/Auster HPDD Wiki Auster])
* [https://wiki.whamcloud.com/display/PUB/Testing+a+Lustre+filesystem#TestingaLustrefilesystem-auster Auster]
|-
 
|sanityn
----
|Tests that verify operations from two clients under normal operating conditions. This is done by mounting the same filesystem twice on a single client, in order to allow a single script/program to execute and verify filesystem operations on multiple "clients" without having to be a distributed program itself.(Source [https://wiki.hpdd.intel.com/display/PUB/Auster HPDD Wiki Auster])
wiki.old.lustre.org pages related to testing:
|-
* [http://wiki.old.lustre.org/index.php/Acceptance_Small_%28acc-sm%29_Testing_on_Lustre Acceptance Small (acc-sm) Testing on Lustre]
|lfsck
* [http://wiki.old.lustre.org/index.php/Testing_Lustre_Code Testing Lustre Code]
|Tests e2fsck and lfsck to detect and fix filesystem corruption. (Source [https://wiki.hpdd.intel.com/display/PUB/Auster HPDD Wiki Auster])
 
|-
[[Category:Testing]]
|liblustre
| Runs a test linked to a liblustre client library. (Source [https://wiki.hpdd.intel.com/display/PUB/Auster HPDD Wiki Auster])
|-
|replay-single
| A set of unit tests that verify recovery after MDS failure. (Source [https://wiki.hpdd.intel.com/display/PUB/Auster HPDD Wiki Auster])
|-
|conf-sanity
|A set of unit tests that verify the configuration tools, and runs Lustre with multiple different setups to ensure correct operation in unusual system configurations. (Source [https://wiki.hpdd.intel.com/display/PUB/Auster HPDD Wiki Auster])
|-
|recovery-small
|A set of unit tests that verify RPC replay after communications failure. (Source [https://wiki.hpdd.intel.com/display/PUB/Auster HPDD Wiki Auster])
|-
|replay-ost-single
| A set of unit tests that verify recovery after OST failure. (Source [https://wiki.hpdd.intel.com/display/PUB/Auster HPDD Wiki Auster])
|-
|replay-dual
|A set of unit tests that verify the recovery from two clients after server failure. (Source [https://wiki.hpdd.intel.com/display/PUB/Auster HPDD Wiki Auster])
|-
|insanity
|A set of tests that verify the multiple concurrent failure conditions. (Source [https://wiki.hpdd.intel.com/display/PUB/Auster HPDD Wiki Auster])
|-
|sanity-quota
|A set of tests that verify filesystem quotas. (Source [https://wiki.hpdd.intel.com/display/PUB/Auster HPDD Wiki Auster])
|}

Revision as of 16:03, 13 November 2020