[lustre-discuss] Testing Lustre

[Aurelien Degremont]

Hello Dmitry,

You can specify variables to tune the test framework behavior. Some of them will skip doing the filesystem setup, you can even specify where the fs is mounted, etc...
Focus on running only sanity.sh

But this will be a long process to tune all variables properly for most tests to pass or be skipped. It may be overkill.

Have a look at https://wiki.lustre.org/TestingLustreCode<https://wiki.lustre.org/TestingLustreCode>

Aurélien
________________________________
De : lustre-discuss <lustre-discuss-bounces at lists.lustre.org> de la part de Dmitry Ganyushin via lustre-discuss <lustre-discuss at lists.lustre.org>
Envoyé : mercredi 4 juin 2025 16:01
À : lustre-discuss at lists.lustre.org <lustre-discuss at lists.lustre.org>
Objet : [lustre-discuss] Testing Lustre

External email: Use caution opening links or attachments

Dear Lustre Community,

I have a question regarding Lustre testing procedures. I have a small test
Lustre file system installed, and I would like to run a few formal tests to be
sure that things are built and configured correctly.

I tried to run the sanity test from the repo using auster, but it looks like the
sanity test tries to build a test file system from scratch including formatting
and other steps which I already have done myself.  I am wondering if it were
possible to set up test configs in a way that only the testing part will be
executed without initialization.

I can comment out the Lustre initialization functions in the test scripts,
and that works for a majority of sanity tests, but I am looking for a less invasive solution.

Thanks in advance for your help

Dmitry Ganyushin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lustre.org/pipermail/lustre-discuss-lustre.org/attachments/20250605/2d79cb8b/attachment.htm>