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 <[email protected]> de la part de Dmitry Ganyushin via lustre-discuss <[email protected]> Envoyé : mercredi 4 juin 2025 16:01 À : [email protected] <[email protected]> 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
_______________________________________________ lustre-discuss mailing list [email protected] http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org
