Workaround for CrayVariablesCheckEiger with CPE 23.12 #190
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
CPE 23.12 replaced the environment variable
CRAY_LIBSCI_PREFIX_DIR
withCRAY_PE_LIBSCI_PREFIX
andCRAY_PE_LIBSCI_PREFIX_DIR
in the modulefilecray-libsci
.Additionally, the name of the
gcc
module loaded byPrgEnv-gnu
is nowgcc-native
(see SPCI-236 for more details).Therefore, the sanity patterns
{envvar_prefix}_PREFIX
and{envvar_prefix}_VERSION
usingenvvar_prefix = self.cray_module.upper().replace('-', '_')
do not work any longer forCrayVariablesCheckEiger
, since the envvar prefix should beCRAY_PE_LIBSCI
forcray-libsci
andGCC
only forgcc-native
.I am providing a quick workaround that simply skips the check of
cray-libsci
andgcc
for the time being.