pick up RISC-V software installations from /cvmfs/dev.eessi.io/riscv for EESSI 2025.06

[bedroge]

Version 2023.06 still redirects to /cvmfs/riscv.eessi.io for RISC-V clients, but for 2025.06 this will make the module use the init scripts and compat layer from software.eessi.io and the software installations from dev.eessi.io/riscv. In order to do that, I've added a eessi_archdetect_prefix variable which is set early, to ensure that it will look for archdetect in the production repo (instead of the dev repo). If the dev repo is not available on the host, it will print an error.

[bedroge]

This seems to work as expected, tested on a RISC-V system:

# first try 2025.06, note that the software dir needs to exist
Singularity> mkdir -p /cvmfs/dev.eessi.io/riscv/versions/2025.06/software/linux/riscv64/generic/software
Singularity> source /cvmfs/software.eessi.io/versions/2025.06/init/lmod/bash

Singularity> ml EESSI/2025.06
This EESSI production version only provides a RISC-V compatibility layer,
software installations are provided by the EESSI development repository at /cvmfs/dev.eessi.io/riscv.

Module for EESSI/2025.06 loaded successfully
Singularity> ml purge


# Try a custom version
Singularity> export EESSI_VERSION_OVERRIDE=2025.06-10
Singularity> ml EESSI/2025.06
This EESSI production version only provides a RISC-V compatibility layer,
software installations are provided by the EESSI development repository at /cvmfs/dev.eessi.io/riscv.

Lmod has detected the following error:  Software directory check for the detected architecture failed 
While processing the following module(s):
    Module fullname  Module Filename
    ---------------  ---------------
    EESSI/2025.06    /cvmfs/software.eessi.io/versions/2025.06/init/modules/EESSI/2025.06.lua

Singularity> mkdir -p /cvmfs/dev.eessi.io/riscv/versions/2025.06-10/software/linux/riscv64/generic/software
Singularity> ml EESSI/2025.06
This EESSI production version only provides a RISC-V compatibility layer,
software installations are provided by the EESSI development repository at /cvmfs/dev.eessi.io/riscv.

Module for EESSI/2025.06-10 loaded successfully

Singularity> echo $EESSI_PREFIX
/cvmfs/dev.eessi.io/riscv/versions/2025.06-10
Singularity> echo $EESSI_SOFTWARE_PATH
/cvmfs/dev.eessi.io/riscv/versions/2025.06-10/software/linux/riscv64/generic


# And, finally, check 2023.06
Singularity> ml EESSI/2023.06
RISC-V architecture detected, but there is no RISC-V support yet in the production repository.
Automatically switching to version 20240402 of the RISC-V development repository /cvmfs/riscv.eessi.io.
For more details about this repository, see https://www.eessi.io/docs/repositories/riscv.eessi.io/. 
Module for EESSI/20240402 loaded successfully

[ocaisa]

LGTM, @bedroge can you just confirm that it works as expected

EDIT: you already have above

[ocaisa]

bot: build repo:eessi.io-2023.06-software instance:eessi-bot-mc-aws for:arch=x86_64/amd/zen2
bot: build repo:eessi.io-2025.06-software instance:eessi-bot-mc-aws for:arch=x86_64/amd/zen2

[eessi-bot-aws]

New job on instance eessi-bot-mc-aws for repository eessi.io-2023.06-software
Building on: amd-zen2
Building for: x86_64/amd/zen2
Job dir: /project/def-users/SHARED/jobs/2025.09/pr_80/92595

date	job status	comment
Sep 26 11:38:31 UTC 2025	submitted	job id 92595 awaits release by job manager
Sep 26 11:39:06 UTC 2025	released	job awaits launch by Slurm scheduler
Sep 26 11:59:04 UTC 2025	running	job 92595 is running
Sep 26 12:02:22 UTC 2025	finished	😁 SUCCESS (click triangle for details) Details ✅ job output file slurm-92595.out ✅ no message matching FATAL: ✅ no message matching ERROR: ✅ no message matching FAILED: ✅ no message matching required modules missing: ✅ found message(s) matching No missing installations ✅ found message matching .tar.gz created! Artefacts eessi-2023.06-software-linux-x86_64-amd-zen2-17588879420.tar.gz size: 0 MiB (3530 bytes) entries: 1 modules under 2023.06/software/linux/x86_64/amd/zen2/modules/all no module files in tarball software under 2023.06/software/linux/x86_64/amd/zen2/software no software packages in tarball reprod directories under 2023.06/software/linux/x86_64/amd/zen2/reprod no reprod directories in tarball other under 2023.06/software/linux/x86_64/amd/zen2 2023.06/init/modules/EESSI/2023.06.lua
Sep 26 12:02:22 UTC 2025	test result	😁 SUCCESS (click triangle for details) ReFrame Summary [ OK ] ( 1/10) EESSI_LAMMPS_lj %device_type=cpu %module_name=LAMMPS/29Aug2024-foss-2023b-kokkos %scale=1_node /aeb2d9df @BotBuildTests:x86_64_amd_zen2+default P: perf: 430.859 timesteps/s (r:0, l:None, u:None) [ OK ] ( 2/10) EESSI_LAMMPS_lj %device_type=cpu %module_name=LAMMPS/2Aug2023_update2-foss-2023a-kokkos %scale=1_node /04ff9ece @BotBuildTests:x86_64_amd_zen2+default P: perf: 436.477 timesteps/s (r:0, l:None, u:None) [ OK ] ( 3/10) EESSI_OSU_coll %benchmark_info=mpi.collective.osu_allreduce %module_name=OSU-Micro-Benchmarks/7.2-gompi-2023b %scale=1_node %device_type=cpu /775175bf @BotBuildTests:x86_64_amd_zen2+default P: latency: 1.85 us (r:0, l:None, u:None) [ OK ] ( 4/10) EESSI_OSU_coll %benchmark_info=mpi.collective.osu_allreduce %module_name=OSU-Micro-Benchmarks/7.1-1-gompi-2023a %scale=1_node %device_type=cpu /52707c40 @BotBuildTests:x86_64_amd_zen2+default P: latency: 1.94 us (r:0, l:None, u:None) [ OK ] ( 5/10) EESSI_OSU_coll %benchmark_info=mpi.collective.osu_alltoall %module_name=OSU-Micro-Benchmarks/7.2-gompi-2023b %scale=1_node %device_type=cpu /b1aacda9 @BotBuildTests:x86_64_amd_zen2+default P: latency: 4.07 us (r:0, l:None, u:None) [ OK ] ( 6/10) EESSI_OSU_coll %benchmark_info=mpi.collective.osu_alltoall %module_name=OSU-Micro-Benchmarks/7.1-1-gompi-2023a %scale=1_node %device_type=cpu /c6bad193 @BotBuildTests:x86_64_amd_zen2+default P: latency: 4.14 us (r:0, l:None, u:None) [ OK ] ( 7/10) EESSI_OSU_pt2pt_CPU %benchmark_info=mpi.pt2pt.osu_latency %module_name=OSU-Micro-Benchmarks/7.2-gompi-2023b %scale=1_node /15cad6c4 @BotBuildTests:x86_64_amd_zen2+default P: latency: 0.6 us (r:0, l:None, u:None) [ OK ] ( 8/10) EESSI_OSU_pt2pt_CPU %benchmark_info=mpi.pt2pt.osu_latency %module_name=OSU-Micro-Benchmarks/7.1-1-gompi-2023a %scale=1_node /6672deda @BotBuildTests:x86_64_amd_zen2+default P: latency: 0.58 us (r:0, l:None, u:None) [ OK ] ( 9/10) EESSI_OSU_pt2pt_CPU %benchmark_info=mpi.pt2pt.osu_bw %module_name=OSU-Micro-Benchmarks/7.2-gompi-2023b %scale=1_node /2a9a47b1 @BotBuildTests:x86_64_amd_zen2+default P: bandwidth: 7371.31 MB/s (r:0, l:None, u:None) [ OK ] (10/10) EESSI_OSU_pt2pt_CPU %benchmark_info=mpi.pt2pt.osu_bw %module_name=OSU-Micro-Benchmarks/7.1-1-gompi-2023a %scale=1_node /1b24ab8e @BotBuildTests:x86_64_amd_zen2+default P: bandwidth: 7253.13 MB/s (r:0, l:None, u:None) [ PASSED ] Ran 10/10 test case(s) from 10 check(s) (0 failure(s), 0 skipped, 0 aborted) Details ✅ job output file slurm-92595.out ✅ no message matching ERROR: ✅ no message matching [\s*FAILED\s*].*Ran .* test case
Sep 26 12:54:03 UTC 2025	uploaded	transfer of eessi-2023.06-software-linux-x86_64-amd-zen2-17588879420.tar.gz to S3 bucket succeeded

[eessi-bot-aws]

New job on instance eessi-bot-mc-aws for repository eessi.io-2025.06-software
Building on: amd-zen2
Building for: x86_64/amd/zen2
Job dir: /project/def-users/SHARED/jobs/2025.09/pr_80/92596

date	job status	comment
Sep 26 11:38:35 UTC 2025	submitted	job id 92596 awaits release by job manager
Sep 26 11:39:04 UTC 2025	released	job awaits launch by Slurm scheduler
Sep 26 11:59:30 UTC 2025	finished	😁 SUCCESS (click triangle for details) Details ✅ job output file slurm-92596.out ✅ no message matching FATAL: ✅ no message matching ERROR: ✅ no message matching FAILED: ✅ no message matching required modules missing: ✅ found message(s) matching No missing installations ✅ found message matching .tar.gz created! Artefacts eessi-2025.06-software-linux-x86_64-amd-zen2-17588878940.tar.gz size: 0 MiB (3532 bytes) entries: 1 modules under 2025.06/software/linux/x86_64/amd/zen2/modules/all no module files in tarball software under 2025.06/software/linux/x86_64/amd/zen2/software no software packages in tarball reprod directories under 2025.06/software/linux/x86_64/amd/zen2/reprod no reprod directories in tarball other under 2025.06/software/linux/x86_64/amd/zen2 2025.06/init/modules/EESSI/2025.06.lua
Sep 26 11:59:30 UTC 2025	test result	😢 FAILURE (click triangle for details) Reason EESSI test suite was not run, test step itself failed to execute. Details ✅ job output file slurm-92596.out ❌ found message matching ERROR: ✅ no message matching [\s*FAILED\s*].*Ran .* test case
Sep 26 12:54:12 UTC 2025	uploaded	transfer of eessi-2025.06-software-linux-x86_64-amd-zen2-17588878940.tar.gz to S3 bucket succeeded

[ocaisa]

Deployment PR merged