-
Notifications
You must be signed in to change notification settings - Fork 15
two more fixes for building RISC-V stacks with a version suffix #140
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
|
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
|
boegel
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
|
deployed, so merging... |
#131 added support for RISC-V version suffixes to the EESSI module file, but somehow I only added this to the RISC-V 2023.06 code. This PR adds the same code to the if statement that runs code for the 2025.06 version.
Also it makes
EESSI-install-software.shlook for easystacks in directories with the version suffix, i.e. instead of having to put the RISC-V 2025.06-001 easystacks ineasystacks/riscv/2025.06we can now useeasystacks/riscv/2025.06-001. That makes more sense to me, as you likely want to start from scratch for a new version suffix (otherwise it will start building all stuff from the old suffix in the very first job).Tested this by entering the job directory of the failed job from #131, setting some environment variables that otherwise the dev repo job script and Slurm would set (
EESSI_COMPAT_LAYER_DIR_OVERRIDE,EASYBUILD_ROBOT_PATHS,EESSI_DEV_PROJECT,SLURM_JOB_ID), applying the changes from this PR, and runningsoftware-layer-scripts/bot/build.sh. This correctly installed EB 5.1.2, EESSI-extend, EB 5.1.1 (used by the easystack), and finally cowsay:So, hopefully, this is really the last PR before we can finally start building for
/cvmfs/dev.eessi.io/riscv... 😄