Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: Lmod integration to use & save user-specified configuration files #176

Open
hagertnl opened this issue Jul 22, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@hagertnl
Copy link
Contributor

Proposing an optional flag to runtests.py (or more accurately, to test_harness_driver.py): --lmod-rc=/path/to/rc.lua

This flag provides the path to a Lua file that sets defaults and hides modules, as described by https://lmod.readthedocs.io/en/latest/093_modulerc.html#modulerc-label . This would enable user-specified default environments, which allows tests to depend on the default modules, instead of specifying specific versions, which would require less test maintenance in the future. We can use the LMOD_MODULERCFILE environment variable to achieve this configuration. Note that this does override the OLCF-specified LMOD_MODULERCFILE, but I think that's a necessary risk -- if you are going to set your own defaults, then it seems right that you would ignore the OLCF-specified defaults or copy those defaults into your own rc.lua.

A best practice would be to program known breakages into the build script, to prevent the test from launching if it is known to fail. For example, if ROCm/5.3.0 has a bug in the runtime library that impacts a test, that test should fail in the build stage if ROCm/5.3.0 is detected.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant