-
Notifications
You must be signed in to change notification settings - Fork 15
Introduce $EESSI_SOFTWARE_LAYER_VERSION_SUFFIX to make build scripts more dynamic
#131
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
trz42
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.
looks good to me. one minor suggestion to improve readability a little.
|
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
|
trz42
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
|
staging PR merged, so I'll go ahead and merge this too... |
I still ran into one more issue with the RISC-V bot, and that's because the build scripts were not flexible enough to handle a version
2025.06-001:$EESSI_VERSIONis used in different scripts for different purposes, and sometimes we need it with the suffix and sometimes without. This PR introduces a$EESSI_SOFTWARE_LAYER_VERSION_SUFFIX, which should solve the issue.The default behavior for non-RISCV systems shouldn't change: the suffix is set to an empty string by both
init/eessi_defaultsand the module, unless $EESSI_OVERRIDE_VERSION contains a suffix.Tested manually on a RISC-V system.