Run unit tests on an updated version of Modules 4 #4415
Conversation
Environment Modules was updated on EL8 from version 4.1.4 to version 4.5.2+patches which can be assimilated to version 4.5.3. Seems interesting to update the modules4 version used in unit_tests CI workflow to match Environment Modules version found in EL8.
test_cray_reset and test_independence tests successively load all Cray* modules. One Cray* module does not unload other Cray* modules loaded which give an inconsistent environment. Environment Modules tool version 4.2 and above does not allow setting up an inconsistent environment without --force option set. To fix test_cray_reset and test_independence tests for Environment Modules tool, environment is purged between each toolchain setup.
xdelaruelle
force-pushed
the
unit_tests_modules4
branch
from
b4e2c2f
to
ae47402
Compare
|
I have disabled "test_toy_toy" when Environment Modules tool is used as the test produces an inconsitent environment. "test_toy_toy" test generates two versions of "toy" module. Both modules express a reflexive conflict (against "toy") and toy/0.0-two loads toy/0.0-one. As these two modules share the same name ( Environment Modules version 4.2 (and above) detects this inconsistency and raise an error unless I am not fully satisfied with the solution of disabling this "test_toy_toy" test for EnvironmentModules but it seemed to be the more pragmatic way to solve this. Another solution would be to rename the second software "toy_toy", but it requires some changes on the test and duplication of files in the repository. It may not be worth it. |
xdelaruelle
force-pushed
the
unit_tests_modules4
branch
from
ae47402
to
e6cf639
Compare
"test_toy_toy" test generates two versions of "toy" module. Both modules
express a reflexive conflict (against "toy") and toy/0.0-two loads
toy/0.0-one.
As these two modules share the same name ("toy") and due to the
reflexive conflict they express, environment obtained when loading
toy/0.0-two is inconsistent as it tries to load toy/0.0-one.
Environment Modules version 4.2 (and above) detects this inconsistency
and raise an error unless --force option is set.
"test_toy_toy" test is adapted to be skipped when Environment Modules
tool is used, as the environment generated by the test produces an error
with this module tool.
xdelaruelle
force-pushed
the
unit_tests_modules4
branch
from
e6cf639
to
12e6154
Compare
Environment Modules was updated on EL8 from version 4.1.4 to version 4.5.2+patches which can be assimilated to version 4.5.3.
Seems interesting to update the modules4 version used in unit_tests CI workflow to match Environment Modules version found in EL8.