take software layer version suffix into account when creating a tarball

[bedroge]

When we build for a version with a suffix (e.g. 2025.06-001), the tarball step should actually check the directory name with the suffix in the overlay's upper dir. Note that it already sources eessi_defaults on line 293, this should set $EESSI_SOFTWARE_LAYER_VERSION_SUFFIX.

[bedroge]

Let's make sure that it doesn't break anything for regular builds.

bot: build repo:eessi.io-2023.06-software instance:eessi-bot-mc-aws for:arch=x86_64/intel/haswell

[eessi-bot-aws]

New job on instance eessi-bot-mc-aws for repository eessi.io-2023.06-software
Building on: intel-haswell
Building for: x86_64/intel/haswell
Job dir: /project/def-users/SHARED/jobs/2025.11/pr_135/107427

date	job status	comment
Nov 24 09:07:46 UTC 2025	submitted	job id 107427 awaits release by job manager
Nov 24 09:08:39 UTC 2025	released	job awaits launch by Slurm scheduler
Nov 24 09:13:48 UTC 2025	running	job 107427 is running
Nov 24 09:17:37 UTC 2025	finished	😁 SUCCESS (click triangle for details) Details ✅ job output file slurm-107427.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.* created! Artefacts eessi-2023.06-software-linux-x86_64-intel-haswell-17639756460.tar.zst size: 0 MiB (73131 bytes) entries: 78 modules under 2023.06/software/linux/x86_64/intel/haswell/modules/all cowsay/3.04.lua software under 2023.06/software/linux/x86_64/intel/haswell/software cowsay/3.04 reprod directories under 2023.06/software/linux/x86_64/intel/haswell/reprod no reprod directories in tarball other under 2023.06/software/linux/x86_64/intel/haswell no other files in tarball
Nov 24 09:17:37 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_intel_haswell+default P: perf: 439.979 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_intel_haswell+default P: perf: 472.541 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_intel_haswell+default P: latency: 3.03 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_intel_haswell+default P: latency: 3.12 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_intel_haswell+default P: latency: 7.85 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_intel_haswell+default P: latency: 5.75 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_intel_haswell+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_intel_haswell+default P: latency: 0.73 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_intel_haswell+default P: bandwidth: 10699.09 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_intel_haswell+default P: bandwidth: 10738.35 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-107427.out ✅ no message matching ERROR: ✅ no message matching [\s*FAILED\s*].*Ran .* test case

[bedroge]

That worked, so let's do the final builds.

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

[bedroge]

Actually, this doesn't require a build+deploy, so I've cancelled the build jobs.