add EESSI/2025.06 module file (+ populate scripts for all CPU targets in `2025.06` software layer) #6

boegel · 2025-06-13T09:05:19Z

This will add the EESSI/2025.06.lua module file to /cvmfs/software.eessi.io/versions/2025.06/init/modules/EESSI/2025.06.lua.test.

Exposing this module file in /cvmfs/software.eessi.io/init/modules is done through symlinking, see EESSI/filesystem-layer#198.
Temporarily hiding this module should also be done in there.

edit: requires:

make sure that copied scripts in init/ and scripts/ use right EESSI version #11

boegel · 2025-06-13T09:06:49Z

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

eessi-bot-aws · 2025-06-13T09:06:54Z

New job on instance eessi-bot-mc-aws for CPU micro-architecture x86_64-amd-zen2 for repository eessi.io-2025.06-software in job dir /project/def-users/SHARED/jobs/2025.06/pr_6/69344

date	job status	comment
Jun 13 09:06:53 UTC 2025	submitted	job id `69344` awaits release by job manager
Jun 13 09:07:48 UTC 2025	released	job awaits launch by Slurm scheduler
Jun 13 09:12:50 UTC 2025	running	job `69344` is running
Jun 13 09:19:57 UTC 2025	finished	😢 FAILURE (click triangle for details) Details ✅ job output file `slurm-69344.out` ✅ no message matching `FATAL:` ❌ found message matching `ERROR:` ✅ no message matching `FAILED:` ✅ no message matching `required modules missing:` ❌ no message matching `No missing installations` ✅ found message matching `.tar.gz created!` Artefacts No artefacts were created or found.
Jun 13 09:19:57 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: 439.666 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: 438.949 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: 2.01 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.81 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.06 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.06 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.61 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.55 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: 7349.48 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: 7464.22 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-69344.out` ❌ found message matching `ERROR:` ✅ no message matching `[\sFAILED\s].Ran . test case`

boegel · 2025-06-13T09:38:50Z

Build currently fails with:

ERROR: /cvmfs/software.eessi.io/versions/2025.06/compat/linux/x86_64 does not exist!

So this will need to wait until compat layer for EESSI 2025.06 has been deployed (cfr. EESSI/compatibility-layer#209)

boegel · 2025-06-13T16:39:17Z

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

eessi-bot-aws · 2025-06-13T16:39:22Z

New job on instance eessi-bot-mc-aws for CPU micro-architecture x86_64-amd-zen2 for repository eessi.io-2025.06-software in job dir /project/def-users/SHARED/jobs/2025.06/pr_6/69361

date	job status	comment
Jun 13 16:39:21 UTC 2025	submitted	job id `69361` awaits release by job manager
Jun 13 16:39:25 UTC 2025	released	job awaits launch by Slurm scheduler
Jun 13 16:40:30 UTC 2025	running	job `69361` is running
Jun 13 16:46:39 UTC 2025	finished	😢 FAILURE (click triangle for details) Details ✅ job output file `slurm-69361.out` ✅ no message matching `FATAL:` ❌ found message matching `ERROR:` ✅ no message matching `FAILED:` ✅ no message matching `required modules missing:` ❌ no message matching `No missing installations` ✅ found message matching `.tar.gz created!` Artefacts `eessi-2025.06-software-linux-x86_64-amd-zen2-17498328010.tar.gz` size: 0 MiB (45 bytes) entries: 0 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 other under 2025.06/software/linux/x86_64/amd/zen2 no other files in tarball
Jun 13 16:46:39 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: 433.534 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: 449.223 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.88 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: 2.28 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: 3.86 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.13 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.57 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.61 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: 7461.64 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: 7358.4 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-69361.out` ❌ found message matching `ERROR:` ✅ no message matching `[\sFAILED\s].Ran . test case`

boegel · 2025-06-13T19:23:14Z

Loading EESSI/2025.06 module fails with:

Lmod has detected the following error: Error found in sourcing script
"/cvmfs/software.eessi.io/versions/2025.06/init/lmod_eessi_archdetect_wrapper.sh":

/cvmfs/software.eessi.io/versions/2025.06/compat/linux/x86_64/bin/bash: line 1:
/cvmfs/software.eessi.io/versions/2025.06/init/lmod_eessi_archdetect_wrapper.sh:
No such file or directory

I think we're calling ./install_scripts.sh too late?

…EESSI/<version> module being loaded

boegel · 2025-06-13T19:29:19Z

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

eessi-bot-aws · 2025-06-13T19:29:25Z

New job on instance eessi-bot-mc-aws for CPU micro-architecture x86_64-amd-zen2 for repository eessi.io-2025.06-software in job dir /project/def-users/SHARED/jobs/2025.06/pr_6/69374

date	job status	comment
Jun 13 19:29:24 UTC 2025	submitted	job id `69374` awaits release by job manager
Jun 13 19:29:59 UTC 2025	released	job awaits launch by Slurm scheduler
Jun 13 19:40:02 UTC 2025	running	job `69374` is running
Jun 13 19:48:09 UTC 2025	finished	😢 FAILURE (click triangle for details) Details ✅ job output file `slurm-69374.out` ✅ no message matching `FATAL:` ❌ found message matching `ERROR:` ✅ no message matching `FAILED:` ✅ no message matching `required modules missing:` ❌ no message matching `No missing installations` ✅ found message matching `.tar.gz created!` Artefacts No artefacts were created or found.
Jun 13 19:48:09 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: 441.965 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: 444.668 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.9 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.78 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: 3.91 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.15 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.56 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.6 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: 7451.28 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: 7332.31 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-69374.out` ❌ found message matching `ERROR:` ✅ no message matching `[\sFAILED\s].Ran . test case`

boegel · 2025-06-14T14:03:03Z

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

eessi-bot-aws · 2025-06-14T14:03:09Z

New job on instance eessi-bot-mc-aws for CPU micro-architecture x86_64-amd-zen2 for repository eessi.io-2025.06-software in job dir /project/def-users/SHARED/jobs/2025.06/pr_6/69583

date	job status	comment
Jun 14 14:03:08 UTC 2025	submitted	job id `69583` awaits release by job manager
Jun 14 14:03:40 UTC 2025	released	job awaits launch by Slurm scheduler
Jun 14 14:08:43 UTC 2025	running	job `69583` is running
Jun 14 14:18:52 UTC 2025	finished	😁 SUCCESS (click triangle for details) Details ✅ job output file `slurm-69583.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-17499102590.tar.gz` size: 14 MiB (14948251 bytes) entries: 17696 modules under 2025.06/software/linux/x86_64/amd/zen2/modules/all `EasyBuild/5.1.0.lua` `EESSI-extend/2025.06-easybuild.lua` software under 2025.06/software/linux/x86_64/amd/zen2/software `EasyBuild/5.1.0` `EESSI-extend/2025.06-easybuild` other under 2025.06/software/linux/x86_64/amd/zen2 `2025.06/init/arch_specs/eessi_arch_arm.spec` `2025.06/init/arch_specs/eessi_arch_ppc.spec` `2025.06/init/arch_specs/eessi_arch_riscv.spec` `2025.06/init/arch_specs/eessi_arch_x86.spec` `2025.06/init/bash` `2025.06/init/easybuild/eb_hooks.py` `2025.06/init/eessi_archdetect.sh` `2025.06/init/eessi_defaults` `2025.06/init/eessi_environment_variables` `2025.06/init/eessi_software_subdir_for_host.py` `2025.06/init/lmod/bash` `2025.06/init/lmod/csh` `2025.06/init/lmod_eessi_archdetect_wrapper_accel.sh` `2025.06/init/lmod_eessi_archdetect_wrapper.sh` `2025.06/init/lmod/fish` `2025.06/init/lmod/ksh` `2025.06/init/lmod/zsh` `2025.06/init/Magic_Castle/bash` `2025.06/init/Magic_Castle/eessi_python3` `2025.06/init/minimal_eessi_env` `2025.06/init/modules/EESSI/2025.06.lua` `2025.06/init/README.md` `2025.06/init/test.py` `2025.06/scripts/gpu_support/nvidia/easystacks/eessi-2023.06-eb-4.9.4-2023a-CUDA-host-injections.yml` `2025.06/scripts/gpu_support/nvidia/easystacks/eessi-2023.06-eb-4.9.4-2023b-CUDA-host-injections.yml` `2025.06/scripts/gpu_support/nvidia/install_cuda_and_libraries.sh` `2025.06/scripts/gpu_support/nvidia/install_cuda_host_injections.sh` `2025.06/scripts/gpu_support/nvidia/link_nvidia_host_libraries.sh` `2025.06/scripts/utils.sh` `.lmod/lmodrc.lua` `.lmod/SitePackage.lua`
Jun 14 14:18:52 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: 433.682 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: 442.999 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.9 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: 2.57 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.02 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.1 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.57 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.59 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: 7404.51 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: 7451.43 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-69583.out` ✅ no message matching `ERROR:` ✅ no message matching `[\sFAILED\s].Ran . test case`

boegel · 2025-06-14T14:53:24Z

We should tweak the contents of the scripts being copied under init/, so the default version corresponds to that EESSI version.
For example

$ grep 2023.06 init/lmod/bash
EESSI_VERSION="${EESSI_VERSION:-2023.06}"

Under scripts/ we should avoid that easystack files for 2023.06 versions are being copied under 2025.06/scripts/gpu_support/nvidia/easystacks

boegel · 2025-06-14T17:40:37Z

We should tweak the contents of the scripts being copied under init/, so the default version corresponds to that EESSI version. For example
$ grep 2023.06 init/lmod/bash
EESSI_VERSION="${EESSI_VERSION:-2023.06}"
Under scripts/ we should avoid that easystack files for 2023.06 versions are being copied under 2025.06/scripts/gpu_support/nvidia/easystacks

Fixed in #11, also included in this PR for testing...

boegel · 2025-06-14T17:40:47Z

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

eessi-bot-aws · 2025-06-14T17:40:53Z

New job on instance eessi-bot-mc-aws for CPU micro-architecture x86_64-amd-zen2 for repository eessi.io-2025.06-software in job dir /project/def-users/SHARED/jobs/2025.06/pr_6/69584

date	job status	comment
Jun 14 17:40:53 UTC 2025	submitted	job id `69584` awaits release by job manager
Jun 14 17:41:12 UTC 2025	released	job awaits launch by Slurm scheduler
Jun 14 17:47:14 UTC 2025	running	job `69584` is running
Jun 14 17:51:18 UTC 2025	finished	😁 SUCCESS (click triangle for details) Details ✅ job output file `slurm-69584.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-17499233430.tar.gz` size: 14 MiB (14950535 bytes) entries: 17696 modules under 2025.06/software/linux/x86_64/amd/zen2/modules/all `EasyBuild/5.1.0.lua` `EESSI-extend/2025.06-easybuild.lua` software under 2025.06/software/linux/x86_64/amd/zen2/software `EasyBuild/5.1.0` `EESSI-extend/2025.06-easybuild` other under 2025.06/software/linux/x86_64/amd/zen2 `2025.06/init/arch_specs/eessi_arch_arm.spec` `2025.06/init/arch_specs/eessi_arch_ppc.spec` `2025.06/init/arch_specs/eessi_arch_riscv.spec` `2025.06/init/arch_specs/eessi_arch_x86.spec` `2025.06/init/bash` `2025.06/init/easybuild/eb_hooks.py` `2025.06/init/eessi_archdetect.sh` `2025.06/init/eessi_defaults` `2025.06/init/eessi_environment_variables` `2025.06/init/eessi_software_subdir_for_host.py` `2025.06/init/lmod/bash` `2025.06/init/lmod/csh` `2025.06/init/lmod_eessi_archdetect_wrapper_accel.sh` `2025.06/init/lmod_eessi_archdetect_wrapper.sh` `2025.06/init/lmod/fish` `2025.06/init/lmod/ksh` `2025.06/init/lmod/zsh` `2025.06/init/Magic_Castle/bash` `2025.06/init/Magic_Castle/eessi_python3` `2025.06/init/minimal_eessi_env` `2025.06/init/modules/EESSI/2025.06.lua` `2025.06/init/README.md` `2025.06/init/test.py` `2025.06/scripts/gpu_support/nvidia/easystacks/eessi-2023.06-eb-4.9.4-2023a-CUDA-host-injections.yml` `2025.06/scripts/gpu_support/nvidia/easystacks/eessi-2023.06-eb-4.9.4-2023b-CUDA-host-injections.yml` `2025.06/scripts/gpu_support/nvidia/install_cuda_and_libraries.sh` `2025.06/scripts/gpu_support/nvidia/install_cuda_host_injections.sh` `2025.06/scripts/gpu_support/nvidia/link_nvidia_host_libraries.sh` `2025.06/scripts/utils.sh` `.lmod/lmodrc.lua` `.lmod/SitePackage.lua`
Jun 14 17:51:18 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-69584.out` ❌ found message matching `ERROR:` ✅ no message matching `[\sFAILED\s].Ran . test case`

boegel · 2025-06-15T08:32:25Z

Note: PR that updates install_script.sh should get merged first (some changes included there are also included here):

make sure that copied scripts in init/ and scripts/ use right EESSI version #11

bedroge · 2025-07-01T14:17:05Z

@boegel can you resolve the conflicts / sync with the main branch?

bedroge · 2025-07-02T17:55:50Z

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

eessi-bot-aws · 2025-07-02T17:55:56Z

New job on instance eessi-bot-mc-aws for CPU micro-architecture x86_64-amd-zen2 for repository eessi.io-2025.06-software in job dir /project/def-users/SHARED/jobs/2025.07/pr_6/73431

date	job status	comment
Jul 02 17:55:55 UTC 2025	submitted	job id `73431` awaits release by job manager
Jul 02 17:56:36 UTC 2025	released	job awaits launch by Slurm scheduler
Jul 02 18:03:39 UTC 2025	running	job `73431` is running
Jul 02 18:06:42 UTC 2025	finished	😁 SUCCESS (click triangle for details) Details ✅ job output file `slurm-73431.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-17514795380.tar.gz` size: 14 MiB (14757524 bytes) entries: 17696 modules under 2025.06/software/linux/x86_64/amd/zen2/modules/all `EasyBuild/5.1.0.lua` `EESSI-extend/2025.06-easybuild.lua` software under 2025.06/software/linux/x86_64/amd/zen2/software `EasyBuild/5.1.0` `EESSI-extend/2025.06-easybuild` other under 2025.06/software/linux/x86_64/amd/zen2 `2025.06/init/arch_specs/eessi_arch_arm.spec` `2025.06/init/arch_specs/eessi_arch_ppc.spec` `2025.06/init/arch_specs/eessi_arch_riscv.spec` `2025.06/init/arch_specs/eessi_arch_x86.spec` `2025.06/init/bash` `2025.06/init/easybuild/eb_hooks.py` `2025.06/init/eessi_archdetect.sh` `2025.06/init/eessi_defaults` `2025.06/init/eessi_environment_variables` `2025.06/init/eessi_software_subdir_for_host.py` `2025.06/init/lmod/bash` `2025.06/init/lmod/csh` `2025.06/init/lmod_eessi_archdetect_wrapper_accel.sh` `2025.06/init/lmod_eessi_archdetect_wrapper.sh` `2025.06/init/lmod/fish` `2025.06/init/lmod/ksh` `2025.06/init/lmod/zsh` `2025.06/init/Magic_Castle/bash` `2025.06/init/Magic_Castle/eessi_python3` `2025.06/init/minimal_eessi_env` `2025.06/init/modules/EESSI/2025.06.lua` `2025.06/init/README.md` `2025.06/init/test.py` `2025.06/scripts/gpu_support/nvidia/easystacks/eessi-2023.06-eb-4.9.4-2023a-CUDA-host-injections.yml` `2025.06/scripts/gpu_support/nvidia/easystacks/eessi-2023.06-eb-4.9.4-2023b-CUDA-host-injections.yml` `2025.06/scripts/gpu_support/nvidia/install_cuda_and_libraries.sh` `2025.06/scripts/gpu_support/nvidia/install_cuda_host_injections.sh` `2025.06/scripts/gpu_support/nvidia/link_nvidia_host_libraries.sh` `2025.06/scripts/utils.sh` `.lmod/lmodrc.lua` `.lmod/SitePackage.lua`
Jul 02 18:06:42 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-73431.out` ❌ found message matching `ERROR:` ✅ no message matching `[\sFAILED\s].Ran . test case`

bedroge · 2025-07-02T18:09:20Z

The tarball contains the following two easystacks:

2025.06/scripts/gpu_support/nvidia/easystacks/eessi-2023.06-eb-4.9.4-2023a-CUDA-host-injections.yml
2025.06/scripts/gpu_support/nvidia/easystacks/eessi-2023.06-eb-4.9.4-2023b-CUDA-host-injections.yml

@ocaisa / @boegel These probably need to go into version-specific subdirs?

bedroge · 2025-07-02T20:27:00Z

I guess we either need to set host_injections_easystacks dynamically by doing something like:

host_injections_easystacks="${TOPDIR}/scripts/gpu_support/nvidia/easystacks/eessi-${EESSI_VERSION}-*.yml

Or, if we prefer to list the required easystacks ourselves, something like:

declare -A host_injections_easystacks=(
    ["2023.06"]="eessi-2023.06-eb-4.9.4-2023a-CUDA-host-injections.yml
                 eessi-2023.06-eb-4.9.4-2023b-CUDA-host-injections.yml"
    ["2025.06"]="eessi-2025.06-eb-5.1.1-2024a-CUDA-host-injections.yml
                 eessi-2025.06-eb-5.1.1-2025a-CUDA-host-injections.yml"
)

copy_files_by_list /a /b ${host_injections_easystacks[${EESSI_VERSION}]}

(you can't have lists inside bash associative arrays, but by having them in a space-separated string, it sort of works like a list, and you can iterate over them; should work as long as we don't use spaces in the filenames)

bedroge · 2025-07-04T12:51:01Z

I was looking for a particular commit/PR that added this code, wondering if there was a reason to have a hardcoded list, and found this comment from @boegel: EESSI/software-layer#772 (review). So, I propose that we use the first approach from my previous comment, and generate the list dynamically, i.e. just ship all easystacks from a (version-specific) directory. I'll make a PR.

bedroge · 2025-07-04T13:35:43Z

@boegel boegel#2 should fix the issue, could you please take a look and merge it? Then we can do another build here.

add EESSI/2025.06 module file

39e8e40

boegel added the 2025.06-software.eessi.io 2025.06 version of software.eessi.io label Jun 13, 2025

Merge branch 'main' into EESSI_2025.06_module

0b4ff7d

call install_scripts.sh earlier, since it installs files required by …

e3fdd59

…EESSI/<version> module being loaded

Merge branch 'fix_install_scripts' into EESSI_2025.06_module

8355def

boegel changed the title ~~add EESSI/2025.06 module file~~ add EESSI/2025.06 module file (+ populate scripts for all CPU targets in 2025.06 software layer) Jun 14, 2025

boegel mentioned this pull request Jun 14, 2025

always copy script if it doesn't exist yet at destination #10

Merged

Merge branch 'init_scripts_fix_version' into EESSI_2025.06_module

cec3627

bedroge mentioned this pull request Jul 2, 2025

Add a top-lever dir init/modules/EESSI containing a symlink to the 2023.06 modulefile EESSI/filesystem-layer#198

Open

Merge branch 'main' into EESSI_2025.06_module

b12c787

bedroge approved these changes Jul 2, 2025

View reviewed changes

add EESSI/2025.06 module file (+ populate scripts for all CPU targets in 2025.06 software layer) #6

Are you sure you want to change the base?

add EESSI/2025.06 module file (+ populate scripts for all CPU targets in 2025.06 software layer) #6

Uh oh!

Conversation

boegel commented Jun 13, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

boegel commented Jun 13, 2025

Uh oh!

eessi-bot-aws bot commented Jun 13, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

boegel commented Jun 13, 2025

Uh oh!

boegel commented Jun 13, 2025

Uh oh!

eessi-bot-aws bot commented Jun 13, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

boegel commented Jun 13, 2025

Uh oh!

boegel commented Jun 13, 2025

Uh oh!

eessi-bot-aws bot commented Jun 13, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

boegel commented Jun 14, 2025

Uh oh!

eessi-bot-aws bot commented Jun 14, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

boegel commented Jun 14, 2025

Uh oh!

boegel commented Jun 14, 2025

Uh oh!

boegel commented Jun 14, 2025

Uh oh!

eessi-bot-aws bot commented Jun 14, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

boegel commented Jun 15, 2025

Uh oh!

bedroge commented Jul 1, 2025

Uh oh!

bedroge commented Jul 2, 2025

Uh oh!

eessi-bot-aws bot commented Jul 2, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

bedroge commented Jul 2, 2025

Uh oh!

bedroge commented Jul 2, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

bedroge commented Jul 4, 2025

Uh oh!

bedroge commented Jul 4, 2025

Uh oh!

Uh oh!

add EESSI/2025.06 module file (+ populate scripts for all CPU targets in `2025.06` software layer) #6

add EESSI/2025.06 module file (+ populate scripts for all CPU targets in `2025.06` software layer) #6

boegel commented Jun 13, 2025 •

edited

Loading

eessi-bot-aws bot commented Jun 13, 2025 •

edited

Loading

eessi-bot-aws bot commented Jun 13, 2025 •

edited

Loading

eessi-bot-aws bot commented Jun 13, 2025 •

edited

Loading

eessi-bot-aws bot commented Jun 14, 2025 •

edited

Loading

eessi-bot-aws bot commented Jun 14, 2025 •

edited

Loading

eessi-bot-aws bot commented Jul 2, 2025 •

edited

Loading

bedroge commented Jul 2, 2025 •

edited

Loading