-
Notifications
You must be signed in to change notification settings - Fork 16
add generic hooks for unsupported modules #91
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
Conversation
…nstead of having them in the generic hook
…tware-layer-scripts into hook_for_unsupported_modules
ocaisa
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, tested for the Zen4 case
|
bot: build repo:eessi.io-2023.06-software instance:eessi-bot-mc-aws for:arch=x86_64/amd/zen2 |
|
New job on instance
|
|
New job on instance
|
This makes the existing zen4 pre_fetch / pre_module / post_module hooks a bit more generic, so that they can also be used for adding dummy modulefiles for other unsupported modules. The function
is_unsupported_moduleis used to determine if something is unsupported, and if so, which environment variable can be used to ignore the LmodError of that module.The hooks are also applied to make a module file with an LmodError for Rust 1.65.0 on A64FX.
Tested locally by building Rust 1.65.0 for A64FX with EESSI-extend:
And also tested by building a 2022b easyconfig for Zen4: