Skip to content

Allow end users to configure EESSI module to be sticky - #41

Merged
bedroge merged 3 commits into
EESSI:mainfrom
ocaisa:tweak_eessi_module
Jul 24, 2025
Merged

Allow end users to configure EESSI module to be sticky#41
bedroge merged 3 commits into
EESSI:mainfrom
ocaisa:tweak_eessi_module

Conversation

@ocaisa

@ocaisa ocaisa commented Jul 24, 2025

Copy link
Copy Markdown
Member

No description provided.

@ocaisa

ocaisa commented Jul 24, 2025

Copy link
Copy Markdown
Member Author

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

@eessi-bot-aws

eessi-bot-aws Bot commented Jul 24, 2025

Copy link
Copy Markdown

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

date job status comment
Jul 24 09:27:53 UTC 2025 submitted job id 78248 awaits release by job manager
Jul 24 09:28:38 UTC 2025 released job awaits launch by Slurm scheduler
Jul 24 09:34:42 UTC 2025 running job 78248 is running
Jul 24 09:38:47 UTC 2025 finished
😁 SUCCESS (click triangle for details)
Details
✅ job output file slurm-78248.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-17533496770.tar.gzsize: 0 MiB (3245 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
Jul 24 09:38:47 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.236 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.251 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.79 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.84 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.9 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.23 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.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: 7169.36 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: 7080.01 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-78248.out
✅ no message matching ERROR:
✅ no message matching [\s*FAILED\s*].*Ran .* test case
Jul 24 14:23:25 UTC 2025 uploaded transfer of eessi-2023.06-software-linux-x86_64-amd-zen2-17533496770.tar.gz to S3 bucket succeeded

@eessi-bot-aws

eessi-bot-aws Bot commented Jul 24, 2025

Copy link
Copy Markdown

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_41/78249

date job status comment
Jul 24 09:27:57 UTC 2025 submitted job id 78249 awaits release by job manager
Jul 24 09:28:36 UTC 2025 released job awaits launch by Slurm scheduler
Jul 24 09:34:40 UTC 2025 running job 78249 is running
Jul 24 09:35:44 UTC 2025 finished
😁 SUCCESS (click triangle for details)
Details
✅ job output file slurm-78249.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-17533496530.tar.gzsize: 0 MiB (3250 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
Jul 24 09:35:44 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-78249.out
❌ found message matching ERROR:
✅ no message matching [\s*FAILED\s*].*Ran .* test case
Jul 24 14:23:33 UTC 2025 uploaded transfer of eessi-2025.06-software-linux-x86_64-amd-zen2-17533496530.tar.gz to S3 bucket succeeded

@bedroge bedroge left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Smart, this is really nice to have!

@bedroge bedroge added 2025.06-software.eessi.io 2025.06 version of software.eessi.io 2023.06-software.eessi.io 2023.06 version of software.eessi.io bot:deploy and removed ready-to-deploy labels Jul 24, 2025
@bedroge

bedroge commented Jul 24, 2025

Copy link
Copy Markdown
Contributor

Would be nice to add this to the docs, maybe under Installation and Configuration -> Configuring EESSI?

And, thinking about this feature, maybe we could also add a family directive (https://lmod.readthedocs.io/en/latest/010_user.html#users-can-only-load-one-compiler-or-mpi-stack-at-a-time) for sites that want to prevent users from mixing the EESSI stack with another stack. We could use an environment variable to let them specify the family name.

family_name = os.getenv("EESSI_MODULE_FAMILY_NAME")
if family_name then
    family(family_name)
end
$ export EESSI_MODULE_FAMILY_NAME=stack
$ ml EESSI/2023.06 
EESSI/2023.06 loaded successfully
$ ml localstack

Lmod is automatically replacing "EESSI/2023.06" with "localstack/1".

Can add that in a follow-up PR.

@bedroge

bedroge commented Jul 24, 2025

Copy link
Copy Markdown
Contributor

Tarballs ingested.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

2023.06-software.eessi.io 2023.06 version of software.eessi.io 2025.06-software.eessi.io 2025.06 version of software.eessi.io bot:deploy

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants