-
Notifications
You must be signed in to change notification settings - Fork 5
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
Add ${VARIANT} to module load log message #58
base: master
Are you sure you want to change the base?
Conversation
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.
Is this actually required? For me the modules load without giving a variant. Maybe this is also a difference between the TCL and LMOD systems. On which one did you try this?
Could be related to this issue. Tried it on JURECA-DC, which has LMOD. |
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.
Still not sure about this one, but since it's a so tiny change and it doesn't break anything I'm inclined to just put it in. I also didn't come across more lmod-vs-tcl things recently.
Giving both would be indeed a good solution. |
Co-authored-by: Dennis Terhorst <[email protected]>
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.
👍 This should be fine for now. Still fighting myself to understand the full implications of the version/variant syntax in LMOD, but that shouldn't stop us here.
@terhorstd Should I merge or close this old PR? |
No description provided.