Rebuild EESSI-extend module to correctly handle EESSI_SITE_INSTALL

[trz42]

The current module EESSI-extend/2023.06-easybuild does not handle the environment setting EESSI_SITE_INSTALL correctly. It just falls back to using the standard CVMFS installation path where versions is replaced with host_injections. This is probably due to an oversight when reviewing PR #371.

Note, when rebuilding this for NESSI, we ran into permission issues when EasyBuild tried to set the permissions of the software after it has been built. Will be interesting to see if we run into the same issue here.

[eessi-bot]

Instance eessi-bot-mc-aws is configured to build:

• arch x86_64/generic for repo eessi-hpc.org-2023.06-compat
• arch x86_64/generic for repo eessi-hpc.org-2023.06-software
• arch x86_64/generic for repo eessi.io-2023.06-compat
• arch x86_64/generic for repo eessi.io-2023.06-software
• arch x86_64/intel/haswell for repo eessi-hpc.org-2023.06-compat
• arch x86_64/intel/haswell for repo eessi-hpc.org-2023.06-software
• arch x86_64/intel/haswell for repo eessi.io-2023.06-compat
• arch x86_64/intel/haswell for repo eessi.io-2023.06-software
• arch x86_64/intel/skylake_avx512 for repo eessi-hpc.org-2023.06-compat
• arch x86_64/intel/skylake_avx512 for repo eessi-hpc.org-2023.06-software
• arch x86_64/intel/skylake_avx512 for repo eessi.io-2023.06-compat
• arch x86_64/intel/skylake_avx512 for repo eessi.io-2023.06-software
• arch x86_64/amd/zen2 for repo eessi-hpc.org-2023.06-compat
• arch x86_64/amd/zen2 for repo eessi-hpc.org-2023.06-software
• arch x86_64/amd/zen2 for repo eessi.io-2023.06-compat
• arch x86_64/amd/zen2 for repo eessi.io-2023.06-software
• arch x86_64/amd/zen3 for repo eessi-hpc.org-2023.06-compat
• arch x86_64/amd/zen3 for repo eessi-hpc.org-2023.06-software
• arch x86_64/amd/zen3 for repo eessi.io-2023.06-compat
• arch x86_64/amd/zen3 for repo eessi.io-2023.06-software
• arch aarch64/generic for repo eessi-hpc.org-2023.06-compat
• arch aarch64/generic for repo eessi-hpc.org-2023.06-software
• arch aarch64/generic for repo eessi.io-2023.06-compat
• arch aarch64/generic for repo eessi.io-2023.06-software
• arch aarch64/neoverse_n1 for repo eessi-hpc.org-2023.06-compat
• arch aarch64/neoverse_n1 for repo eessi-hpc.org-2023.06-software
• arch aarch64/neoverse_n1 for repo eessi.io-2023.06-compat
• arch aarch64/neoverse_n1 for repo eessi.io-2023.06-software
• arch aarch64/neoverse_v1 for repo eessi-hpc.org-2023.06-compat
• arch aarch64/neoverse_v1 for repo eessi-hpc.org-2023.06-software
• arch aarch64/neoverse_v1 for repo eessi.io-2023.06-compat
• arch aarch64/neoverse_v1 for repo eessi.io-2023.06-software

[eessi-bot]

Instance eessi-bot-mc-azure is configured to build:

• arch x86_64/amd/zen4 for repo eessi-hpc.org-2023.06-compat
• arch x86_64/amd/zen4 for repo eessi-hpc.org-2023.06-software
• arch x86_64/amd/zen4 for repo eessi.io-2023.06-compat
• arch x86_64/amd/zen4 for repo eessi.io-2023.06-software

[trz42]

bot: build inst:aws repo:eessi.io-2023.06-software arch:zen2

[eessi-bot]

Updates by the bot instance eessi-bot-mc-aws (click for details)

• received bot command build inst:aws repo:eessi.io-2023.06-software arch:zen2 from trz42

  • expanded format: build instance:aws repository:eessi.io-2023.06-software architecture:zen2

• handling command build instance:aws repository:eessi.io-2023.06-software architecture:zen2 resulted in:

  • submitted job 11109, for details & status see Rebuild EESSI-extend module to correctly handle EESSI_SITE_INSTALL #582 (comment)

[eessi-bot]

Updates by the bot instance eessi-bot-mc-azure (click for details)

• received bot command build inst:aws repo:eessi.io-2023.06-software arch:zen2 from trz42

  • expanded format: build instance:aws repository:eessi.io-2023.06-software architecture:zen2

• handling command build instance:aws repository:eessi.io-2023.06-software architecture:zen2 resulted in:

  • no jobs were submitted

[eessi-bot]

New job on instance eessi-bot-mc-aws for architecture x86_64-amd-zen2 for repository eessi.io-2023.06-software in job dir /project/def-users/SHARED/jobs/2024.05/pr_582/11109

date	job status	comment
May 20 16:52:19 UTC 2024	submitted	job id 11109 awaits release by job manager
May 20 16:52:28 UTC 2024	released	job awaits launch by Slurm scheduler
May 20 16:57:31 UTC 2024	running	job 11109 is running
May 20 17:02:36 UTC 2024	finished	😢 FAILURE (click triangle for details) Details ✅ job output file slurm-11109.out ❌ found message matching ERROR: ❌ found 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-1716224271.tar.gz size: 0 MiB (2784 bytes) entries: 3 modules under 2023.06/software/linux/x86_64/amd/zen2/modules/all EESSI-extend/2023.06-easybuild.lua software under 2023.06/software/linux/x86_64/amd/zen2/software no software packages in tarball other under 2023.06/software/linux/x86_64/amd/zen2 no other files in tarball
May 20 17:02:36 UTC 2024	test result	😁 SUCCESS (click triangle for details) ReFrame Summary [ PASSED ] Ran 10/10 test case(s) from 10 check(s) (0 failure(s), 0 skipped, 0 aborted) Details ✅ job output file slurm-11109.out ❌ found message matching ERROR: ✅ no message matching [\s*FAILED\s*].*Ran .* test case

[ocaisa]

The original behaviour is deliberate so we can create well defined symlinks for the CUDA installation, but maybe I need to rethink this a bit, I guess we could be a bit more loose given we unbreak those links in a very specific way via scripts

[ocaisa]

This path is also used to immediately expose the site modules via our initialisation scripts

[trz42]

Should have used EESSI_PROJECT_INSTALL, so this was a misunderstanding on my side. Will close the PR.