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

Workaround for CrayVariablesCheckEiger with CPE 23.12 #190

Merged
merged 1 commit into from
Apr 26, 2024

Conversation

lucamar
Copy link
Collaborator

@lucamar lucamar commented Apr 25, 2024

CPE 23.12 replaced the environment variable CRAY_LIBSCI_PREFIX_DIR with CRAY_PE_LIBSCI_PREFIX and CRAY_PE_LIBSCI_PREFIX_DIR in the modulefile cray-libsci.
Additionally, the name of the gcc module loaded by PrgEnv-gnu is now gcc-native (see SPCI-236 for more details).

Therefore, the sanity patterns {envvar_prefix}_PREFIX and {envvar_prefix}_VERSION using envvar_prefix = self.cray_module.upper().replace('-', '_') do not work any longer for CrayVariablesCheckEiger, since the envvar prefix should be CRAY_PE_LIBSCI for cray-libsci and GCC only for gcc-native.

I am providing a quick workaround that simply skips the check of cray-libsci and gcc for the time being.

@lucamar lucamar added the bugfix label Apr 25, 2024
@lucamar lucamar requested review from ekouts and teojgo April 25, 2024 08:22
@lucamar lucamar self-assigned this Apr 25, 2024
@lucamar lucamar merged commit 28ae64f into eth-cscs:main Apr 26, 2024
2 checks passed
@lucamar lucamar deleted the fix-environ_check branch April 26, 2024 09:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants