Skip to content

Conversation

@trz42
Copy link
Contributor

@trz42 trz42 commented Oct 5, 2025

The init script for csh, e.g., /cvmfs/software.eessi.io/versions/2023.06/init/lmod/csh, wasn't working properly (some syntax issues with oneliners for if-then-endif constructs as well as slightly off syntax for running commands (csh uses backticks and does not support $(...) syntax).

CI for csh was fixed, mostly by adjusting to different syntax required and working around that - in non-interactive shells - aliases (such as module) aren't retained for subsequent commands after sourcing the init script. Some polishing was applied to the test script (test_init_scripts.sh) as well (mostly replacing tabs with spaces).

Finally, installation of CernVM-FS (and other packages) was sped up by preventing the processing of the man-db trigger. Unless we need man pages in CI this should be fine. Note, only for the workflow tests_init_module.yml.

- name: Check out software-layer repository
uses: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11 # v4.1.1

- name: Avoid processing man-db trigger
Copy link
Member

Choose a reason for hiding this comment

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

This is good, I'm going to steal this for the EESSI GitHub Action

Copy link
Contributor

Choose a reason for hiding this comment

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

Is the slow-down caused by the sudo apt install zsh ksh fish tcsh below?

Copy link
Member

@ocaisa ocaisa Oct 9, 2025

Choose a reason for hiding this comment

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

It's a general thing, slow is relative, it typically 20-30 second for updating man-db, which we will never use so might as well disable it.

@trz42
Copy link
Contributor Author

trz42 commented Oct 9, 2025

@MaKaNu or @ocaisa is this PR something you could have look into? Asking you both because you have been developing the csh init script originally.

Copy link
Contributor

@MaKaNu MaKaNu left a comment

Choose a reason for hiding this comment

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

Looks fine from my side. Congrats for taming this csh.

Copy link
Contributor

Choose a reason for hiding this comment

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

@trz42 it seems you are way more talented than me, to handle csh error message.

After all the "Illegal variable name." and "then: then/endif not found" error messages, I am happy to see this script finally working correctly.

Copy link
Member

@ocaisa ocaisa left a comment

Choose a reason for hiding this comment

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

LGTM, now needs to be deployed...

@ocaisa
Copy link
Member

ocaisa commented Oct 9, 2025

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

@eessi-bot-aws
Copy link

eessi-bot-aws bot commented Oct 9, 2025

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.10/pr_102/95476

date job status comment
Oct 09 08:53:59 UTC 2025 submitted job id 95476 awaits release by job manager
Oct 09 08:54:36 UTC 2025 released job awaits launch by Slurm scheduler
Oct 09 08:59:49 UTC 2025 finished
😁 SUCCESS (click triangle for details)
Details
✅ job output file slurm-95476.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-17600003740.tar.gzsize: 0 MiB (522 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/lmod/csh
Oct 09 08:59:49 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-95476.out
❌ found message matching ERROR:
✅ no message matching [\s*FAILED\s*].*Ran .* test case
Oct 09 09:05:49 UTC 2025 uploaded transfer of eessi-2025.06-software-linux-x86_64-amd-zen2-17600003740.tar.gz to S3 bucket succeeded

@eessi-bot-aws
Copy link

eessi-bot-aws bot commented Oct 9, 2025

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.10/pr_102/95477

date job status comment
Oct 09 08:54:03 UTC 2025 submitted job id 95477 awaits release by job manager
Oct 09 08:54:34 UTC 2025 released job awaits launch by Slurm scheduler
Oct 09 08:59:46 UTC 2025 running job 95477 is running
Oct 09 09:02:57 UTC 2025 finished
😁 SUCCESS (click triangle for details)
Details
✅ job output file slurm-95477.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-17600004000.tar.gzsize: 0 MiB (524 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/lmod/csh
Oct 09 09:02: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: 429.936 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: 440.685 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.84 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.8 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.96 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.3 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.58 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.56 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: 7343.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: 7426.91 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-95477.out
✅ no message matching ERROR:
✅ no message matching [\s*FAILED\s*].*Ran .* test case
Oct 09 09:05:57 UTC 2025 uploaded transfer of eessi-2023.06-software-linux-x86_64-amd-zen2-17600004000.tar.gz to S3 bucket succeeded

@ocaisa
Copy link
Member

ocaisa commented Oct 9, 2025

Deployment PR merged

@ocaisa ocaisa merged commit 706f9e8 into EESSI:main Oct 9, 2025
64 checks passed
@trz42
Copy link
Contributor Author

trz42 commented Oct 9, 2025

Thanks @MaKaNu and @ocaisa for reviewing and deploying the updated csh init script.

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants