Workaround for LMOD only allowing a single hook to be registered, which made our first hook unused #490

casparvl · 2024-03-04T16:00:27Z

Use LMOD_CONFIG_DIR instead of LMOD_RC to allow user overrides of what we specify in our RC file, see search order on https://lmod.readthedocs.io/en/latest/145_properties.html?highlight=lmod_rc#the-properties-file-lmodrc-lua . Also, prefix our hooks with eessi_ to avoid unintentional clashes in namespace between site lmod configuration and eessi lmod configuration

…t we specify in our RC file, see search order on https://lmod.readthedocs.io/en/latest/145_properties.html?highlight=lmod_rc#the-properties-file-lmodrc-lua . Also, prefix our hooks with eessi_ to avoid unintentional clashes in namespace between site lmod configuration and eessi lmod configuration

eessi-bot-aws · 2024-03-04T16:00:31Z

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

…a hook. Lmod only permits the registration of a single function, trying to register a second function will just overwrite the first, as can be seen from https://github.com/TACC/Lmod/blob/a97d68193a6f32ebca4b4bd70dac0f6ac8fddefe/src/Hook.lua#L87

casparvl · 2024-03-05T09:43:59Z

Let me test first if I can indeed extend this hook... if extending it doesn't work anyway, the eessi_load_hook might as well be made a local function.

casparvl · 2024-03-05T13:05:14Z

I can extend this hook. A solution that works is to have in the EESSI lmodrc file:

-- Combine both functions into a single one, as we can only register one function as load hook in lmod
-- Also: make it non-local, so it can be imported and extended by other lmodrc files if needed
function eessi_load_hook(t)
    eessi_cuda_enabled_load_hook(t)
    eessi_openmpi_load_hook(t)
end

hook.register("load", eessi_load_hook)

And then in the site-specific lmodrc file:

lmod_config_dir = os.getenv("LMOD_CONFIG_DIR")
dofile(lmod_config_dir.."/lmodrc.lua")

local function combined_load_hook(t)
    eessi_load_hook(t)
    site_specific_hook_a(t)
end
hook.register("load", combined_load_hook)

(N.B. this is a minimal code example, in reality you'd want to do checking if LMOD_CONFIG_DIR is defined, if lmod_config_dir.."/lmodrc.lua" exists, etc).

While this works and is a solution we can use already today, I've also opened a discussion upstream to see if lmod can be extended to facilitate this in a more natural way: TACC/Lmod#694

ocaisa · 2024-03-05T15:42:50Z

Updating the Lmod version is going to take a while, I suggest we make this available now as it helps record what the necessary steps are on top of anything else.

It's no longer WIP, is it?

casparvl · 2024-03-05T16:52:49Z

You're right, it isn't. I wanted to test it first, but my message from 3 hours ago was the conclusion that that works :D so, this is ready for review.

casparvl · 2024-03-05T17:10:43Z

One thing I'm wondering: should we set LMOD_RC to .../host_injections/.lmod by default? As a site, I probably want this LMOD_RC to be set if (and only if) my user is using the EESSI software stack... How else would I achieve that, other than it being set in the EESSI init script?

This way, I can just put a local lmodrc.lua file in .../host_injections/.lmod and be done with it - nothing else needed from the host site.

…t LMOD_RC

casparvl · 2024-03-05T17:16:30Z

To answer my own question: yes, I think we should do this, and I added it in the commit. Our docs should then just say "If you want to customize lmod behaviour for the EESSI environment, place an lmodrc.lua in host_injections/.lmod" or something of that nature.

ocaisa · 2024-03-05T18:14:57Z

init/eessi_environment_variables

            show_msg "Found Lmod configuration file at $LMOD_RC"
          else
            error "Lmod configuration file not found at $LMOD_RC"
          fi
+          # Allow for site-specific lmod configuration
+          host_lmod_rc="$EESSI_CVMFS_REPO"/host_injections/.lmod/lmodrc.lua


I like the idea in principle, but I'd make it sit within a host_injections equivalent of LMOD_CONFIG_DIR

You mean: nested, so that you have e.g. a /cvmfs/software.eessi.io/host_injections/2023.06/software/linux/x86_64/amd/zen2/.lmod/lmodrc.lua ?

We could. But do you really need to be able to make architecture-specific hooks? In EESSI itself, we only make one hook file with create_lmodrc.py and use logic to do architecture specific things like if (moduleName == "OpenMPI") and (cpuTarget == "aarch64/neoverse_v1") then .... Then we just duplicate the lmodrc.lua to all prefixes

The downside of having this nested in an architecture prefix is that you might need to do a lot of duplication (or at the very least symlinking) as a host site if you have a heterogenous system. For the Snellius system at SURF, it'd already mean putting the same lmodrc.lua in two different prefixes today, and if we have a zen4 tree tomorrow, I'll also need to remember to deploy it there...

On an arch specific level perhaps not, but at least we should use ${EESSI_PREFIX/versions/host_injections} (i.e., /cvmfs/software.eessi.io/host_injections/2023.06)

casparvl · 2024-03-06T10:53:38Z

I'm working on the upstream issue of allowing the registration of multiple hooks of the same type by putting them into a table (instead of overwriting). In the process, I have installed a newer version of lmod locally, and I'm seeing that my hooks are being called way less often:

{EESSI 2023.06} [casparl@gcn6 ~]$ module load OSU-Micro-Benchmarks/7.2-gompi-2023a-CUDA-12.1.1
Loading eessi hooks
in OpenMPI: Loading GCCcore
in OpenMPI: Loading GCC
in OpenMPI: Loading numactl
in OpenMPI: Loading libxml2
in OpenMPI: Loading libpciaccess
in OpenMPI: Loading hwloc
in OpenMPI: Loading OpenSSL
in OpenMPI: Loading libevent
in OpenMPI: Loading UCX
in OpenMPI: Loading libfabric
in OpenMPI: Loading PMIx
in OpenMPI: Loading UCC
in OpenMPI: Loading OpenMPI
in OpenMPI: Loading gompi
in OpenMPI: Loading GDRCopy
in OpenMPI: Loading UCX-CUDA
in OpenMPI: Loading NCCL
in OpenMPI: Loading UCC-CUDA
in OpenMPI: Loading OSU-Micro-Benchmarks
{EESSI 2023.06} [casparl@gcn6 software-layer]$ module --version

Modules based on Lua: Version 8.7.23  2023-03-29 17:19 -05:00
    by Robert McLay mclay@tacc.utexas.edu

{EESSI 2023.06} [casparl@gcn6 ~]$ vi .lmodrc.lua
{EESSI 2023.06} [casparl@gcn6 ~]$ source $HOME/lmod_install/lmod/lmod/init/bash
{EESSI 2023.06} [casparl@gcn6 ~]$ echo $LMOD_CMD
/home/casparl/lmod_install/lmod/lmod/libexec/lmod
{EESSI 2023.06} [casparl@gcn6 ~]$ module load OSU-Micro-Benchmarks/7.2-gompi-2023a-CUDA-12.1.1
Loading eessi hooks
in OpenMPI: Loading OSU-Micro-Benchmarks
{EESSI 2023.06} [casparl@gcn6 ~]$ module purge
Loading eessi hooks
{EESSI 2023.06} [casparl@gcn6 ~]$ module load OSU-Micro-Benchmarks/7.2-gompi-2023a-CUDA-12.1.1
Loading eessi hooks
in OpenMPI: Loading UCX-CUDA
in OpenMPI: Loading NCCL
in OpenMPI: Loading UCC-CUDA
in OpenMPI: Loading OSU-Micro-Benchmarks
{EESSI 2023.06} [casparl@gcn6 ~]$ module --version

Modules based on Lua: Version 8.7.34 (a97d6819) 2024-01-05 19:34 -07:00
    by Robert McLay mclay@tacc.utexas.edu

It seems the load hook is now only called if for modules with the GPU properties assigned. I'm wondering if this may be the result of a change in Lmod of when the lmodrc.lua files are sourced/used. As I learned in the Lmod monthly meeting, they are not the designated place for hooks: strictly speaking, they are only there for defining custom module properties (see https://lmod.readthedocs.io/en/latest/145_properties.html?highlight=lmodrc ). I can imagine Lmod now does something like "does this module have a property?" and only then source the lmodrc files to get the definition of those properties. This is more efficient, since it means these lmodrc files don't need to be read for every module.

The documented place to specify hooks is Site_Package.lua, see https://lmod.readthedocs.io/en/latest/170_hooks.html?highlight=hook#hook-functions . The disadvantage: there is no hierarchy in this, you can only ever have one Site_Package.lua. Of course, we could create a Site_Package.lua in EESSI and have that source a Site_Package.lua from some prefix in host_injections...

I'll confirm if the version is the issue by installing different versions of lmod and seeing if I get the original behaviour back...

casparvl · 2024-03-06T10:58:41Z

Ok, I'm stumped. I installed the 8.7.23 version that we also have in the compat layer from a git clone:

 1097  git checkout 8.7.23
 1098  ./configure --prefix $HOME/lmod_install
 1099  make install

Running with that installation, I still only see the modules with a GPU property invoking the hook:

{EESSI 2023.06} [casparl@gcn6 ~]$ module --version

Modules based on Lua: Version 8.7.24  2023-05-04 15:12 -05:00
    by Robert McLay mclay@tacc.utexas.edu

{EESSI 2023.06} [casparl@gcn6 ~]$ module purge
{EESSI 2023.06} [casparl@gcn6 ~]$ module load OSU-Micro-Benchmarks/7.2-gompi-2023a-CUDA-12.1.1
Load hook B called on UCX-CUDA
Load hook B called on NCCL
Load hook B called on UCC-CUDA
Load hook B called on OSU-Micro-Benchmarks

Why? What's different? I don't know...

casparvl · 2024-03-06T11:37:34Z

Inspecting the debugging output with:

module --debug=3 load OSU-Micro-Benchmarks/7.2-gompi-2023a-CUDA-12.1.1 2>&1 | less

I find:

                                  add_property(arch, gpu){
                                    MT:add_property("UCX-CUDA", "arch", "gpu"){
                                      ReadLmodRC:singleton(){
                                      } ReadLmodRC:singleton
                                      ReadLmodRC:validPropValue("arch", "gpu", t){
                                      } ReadLmodRC:validPropValue
                                    } MT:add_property
                                  } add_property

I.e. it is indeed the add_property in the module which causes ReadLmodRC:singleton() to be invoked. This then triggers a read of all the LmodRC files in the documented order. Now my only question is: what triggers this ReadLmodRC:singleton() for our EESSI installation? That seems to be the following:

          Hub:load(mA={OSU-Micro-Benchmarks/7.2-gompi-2023a-CUDA-12.1.1}){
            Hub:load i: 1, userName: OSU-Micro-Benchmarks/7.2-gompi-2023a-CUDA-12.1.1
            Cache:singleton(){
              Cache:l_new(){
                ReadLmodRC:singleton(){
                } ReadLmodRC:singleton
                #scDescriptT: 3
                Adding: dir: /cvmfs/software.eessi.io/versions/2023.06/software/linux/x86_64/amd/zen2/.lmod/cache, timestamp: 1709303487
                Adding: dir: /cvmfs/software.eessi.io/versions/2023.06/software/linux/x86_64/amd/zen2/.lmod/cache, timestamp: 1709303487
              } Cache:l_new
              s_cache.buildCache: nil
            } Cache:singleton

Which indeed happens very early in the trace. It is part of initializing the Cache:singleton(). In that sense, we are just lucky that it is being called before any of the module load's are called, i.e. that the hooks are registered 'in time'.

casparvl · 2024-03-06T14:02:13Z

FYI: I made two PRs with two possible approaches for supporting registration of more than one function as a hook:
TACC/Lmod#695
TACC/Lmod#696
Whichever of those two approaches we go down, it should make adding (appending) site-customized hooks a bit easier... :)

…tware.eessi.io/host_injections/2023.06/.lmod/lmodrc.lua

init/eessi_environment_variables

ocaisa · 2024-03-06T14:48:13Z

We'll have to make the switch to using SitePackage.lua at some point (issue opened in #491), but this fix is what we need today

ocaisa · 2024-03-06T14:56:12Z

bot: build repo:eessi.io-2023.06-software arch:x86_64/amd/zen3

eessi-bot-aws · 2024-03-06T14:56:15Z

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

received bot command build repo:eessi.io-2023.06-software arch:x86_64/amd/zen3 from ocaisa
- expanded format: build repository:eessi.io-2023.06-software architecture:x86_64/amd/zen3
handling command build repository:eessi.io-2023.06-software architecture:x86_64/amd/zen3 resulted in:
- submitted job 7186, for details & status see Workaround for LMOD only allowing a single hook to be registered, which made our first hook unused #490 (comment)

eessi-bot-aws · 2024-03-06T14:56:19Z

New job on instance eessi-bot-mc-aws for architecture x86_64-amd-zen3 for repository eessi.io-2023.06-software in job dir /project/def-users/SHARED/jobs/2024.03/pr_490/7186

date	job status	comment
Mar 06 14:56:18 UTC 2024	submitted	job id `7186` awaits release by job manager
Mar 06 14:56:33 UTC 2024	released	job awaits launch by Slurm scheduler
Mar 06 15:01:34 UTC 2024	finished	😁 SUCCESS (click triangle for details) Details ✅ job output file `slurm-7186.out` ✅ 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-zen3-1709737287.tar.gz` size: 0 MiB (186175 bytes) entries: 4 modules under 2023.06/software/linux/x86_64/amd/zen3/modules/all no module files in tarball software under 2023.06/software/linux/x86_64/amd/zen3/software no software packages in tarball other under 2023.06/software/linux/x86_64/amd/zen3 `.lmod/cache/spiderT.lua` `.lmod/cache/spiderT.luac_5.1` `.lmod/cache/timestamp` `.lmod/lmodrc.lua`
Mar 06 15:01:34 UTC 2024	test result	(no tests yet)

init/eessi_environment_variables

ocaisa

Meant to request a change in last review

ocaisa · 2024-03-06T15:11:31Z

@casparvl The changes to the initialisation script are not being picked up (according to #490 (comment)). I'm guessing this is deliberate behaviour of our tarring script...but I don't know how to deal with it.

ocaisa · 2024-03-06T16:57:40Z

@casparvl Thinking about this again, I would revert all your changes to init/eessi_environment_variables and we focus solely on fixing the immediate problem. We can't integrate them anyway without jumping through some hoops, and in fact they can be part of the follow-up PR to move to using SitePackage.lua and setting LMOD_PACKAGE_PATH

casparvl · 2024-03-07T13:44:56Z

Also true, ok, I'm stripping that and limiting it to the actual fix.

…ug fix only. We can follow up properly using SitePackage.lua instead

ocaisa · 2024-03-07T13:55:59Z

bot: build repo:eessi.io-2023.06-software

eessi-bot-aws · 2024-03-07T13:56:02Z

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

received bot command build repo:eessi.io-2023.06-software from ocaisa
- expanded format: build repository:eessi.io-2023.06-software
handling command build repository:eessi.io-2023.06-software resulted in:
- submitted job 7246, for details & status see Workaround for LMOD only allowing a single hook to be registered, which made our first hook unused #490 (comment)
- submitted job 7247, for details & status see Workaround for LMOD only allowing a single hook to be registered, which made our first hook unused #490 (comment)
- submitted job 7248, for details & status see Workaround for LMOD only allowing a single hook to be registered, which made our first hook unused #490 (comment)
- submitted job 7249, for details & status see Workaround for LMOD only allowing a single hook to be registered, which made our first hook unused #490 (comment)
- submitted job 7250, for details & status see Workaround for LMOD only allowing a single hook to be registered, which made our first hook unused #490 (comment)
- submitted job 7251, for details & status see Workaround for LMOD only allowing a single hook to be registered, which made our first hook unused #490 (comment)
- submitted job 7252, for details & status see Workaround for LMOD only allowing a single hook to be registered, which made our first hook unused #490 (comment)
- submitted job 7253, for details & status see Workaround for LMOD only allowing a single hook to be registered, which made our first hook unused #490 (comment)

eessi-bot-aws · 2024-03-07T13:56:17Z

New job on instance eessi-bot-mc-aws for architecture x86_64-generic for repository eessi.io-2023.06-software in job dir /project/def-users/SHARED/jobs/2024.03/pr_490/7246

date	job status	comment
Mar 07 13:56:16 UTC 2024	submitted	job id `7246` awaits release by job manager
Mar 07 13:56:37 UTC 2024	released	job awaits launch by Slurm scheduler
Mar 07 14:02:50 UTC 2024	running	job `7246` is running
Mar 07 14:03:58 UTC 2024	finished	😁 SUCCESS (click triangle for details) Details ✅ job output file `slurm-7246.out` ✅ 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-generic-1709820182.tar.gz` size: 0 MiB (187255 bytes) entries: 4 modules under 2023.06/software/linux/x86_64/generic/modules/all no module files in tarball software under 2023.06/software/linux/x86_64/generic/software no software packages in tarball other under 2023.06/software/linux/x86_64/generic `.lmod/cache/spiderT.lua` `.lmod/cache/spiderT.luac_5.1` `.lmod/cache/timestamp` `.lmod/lmodrc.lua`
Mar 07 14:03:58 UTC 2024	test result	(no tests yet)
Mar 07 14:09:02 UTC 2024	uploaded	transfer of `eessi-2023.06-software-linux-x86_64-generic-1709820182.tar.gz` to S3 bucket succeeded

eessi-bot-aws · 2024-03-07T13:56:18Z

New job on instance eessi-bot-mc-aws for architecture x86_64-intel-haswell for repository eessi.io-2023.06-software in job dir /project/def-users/SHARED/jobs/2024.03/pr_490/7247

date	job status	comment
Mar 07 13:56:18 UTC 2024	submitted	job id `7247` awaits release by job manager
Mar 07 13:56:39 UTC 2024	released	job awaits launch by Slurm scheduler
Mar 07 14:03:53 UTC 2024	running	job `7247` is running
Mar 07 14:04:59 UTC 2024	finished	😁 SUCCESS (click triangle for details) Details ✅ job output file `slurm-7247.out` ✅ 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-intel-haswell-1709820237.tar.gz` size: 0 MiB (187544 bytes) entries: 4 modules under 2023.06/software/linux/x86_64/intel/haswell/modules/all no module files in tarball software under 2023.06/software/linux/x86_64/intel/haswell/software no software packages in tarball other under 2023.06/software/linux/x86_64/intel/haswell `.lmod/cache/spiderT.lua` `.lmod/cache/spiderT.luac_5.1` `.lmod/cache/timestamp` `.lmod/lmodrc.lua`
Mar 07 14:04:59 UTC 2024	test result	(no tests yet)
Mar 07 14:09:21 UTC 2024	uploaded	transfer of `eessi-2023.06-software-linux-x86_64-intel-haswell-1709820237.tar.gz` to S3 bucket succeeded

eessi-bot-aws · 2024-03-07T13:56:20Z

New job on instance eessi-bot-mc-aws for architecture x86_64-intel-skylake_avx512 for repository eessi.io-2023.06-software in job dir /project/def-users/SHARED/jobs/2024.03/pr_490/7248

date	job status	comment
Mar 07 13:56:19 UTC 2024	submitted	job id `7248` awaits release by job manager
Mar 07 13:56:41 UTC 2024	released	job awaits launch by Slurm scheduler
Mar 07 14:05:01 UTC 2024	finished	😁 SUCCESS (click triangle for details) Details ✅ job output file `slurm-7248.out` ✅ 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-intel-skylake_avx512-1709820265.tar.gz` size: 0 MiB (187749 bytes) entries: 4 modules under 2023.06/software/linux/x86_64/intel/skylake_avx512/modules/all no module files in tarball software under 2023.06/software/linux/x86_64/intel/skylake_avx512/software no software packages in tarball other under 2023.06/software/linux/x86_64/intel/skylake_avx512 `.lmod/cache/spiderT.lua` `.lmod/cache/spiderT.luac_5.1` `.lmod/cache/timestamp` `.lmod/lmodrc.lua`
Mar 07 14:05:01 UTC 2024	test result	(no tests yet)
Mar 07 14:09:40 UTC 2024	uploaded	transfer of `eessi-2023.06-software-linux-x86_64-intel-skylake_avx512-1709820265.tar.gz` to S3 bucket succeeded

eessi-bot-aws · 2024-03-07T13:56:21Z

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.03/pr_490/7249

date	job status	comment
Mar 07 13:56:20 UTC 2024	submitted	job id `7249` awaits release by job manager
Mar 07 13:56:33 UTC 2024	released	job awaits launch by Slurm scheduler
Mar 07 14:02:46 UTC 2024	running	job `7249` is running
Mar 07 14:03:54 UTC 2024	finished	😁 SUCCESS (click triangle for details) Details ✅ job output file `slurm-7249.out` ✅ 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-1709820180.tar.gz` size: 0 MiB (187303 bytes) entries: 4 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 other under 2023.06/software/linux/x86_64/amd/zen2 `.lmod/cache/spiderT.lua` `.lmod/cache/spiderT.luac_5.1` `.lmod/cache/timestamp` `.lmod/lmodrc.lua`
Mar 07 14:03:54 UTC 2024	test result	(no tests yet)
Mar 07 14:09:59 UTC 2024	uploaded	transfer of `eessi-2023.06-software-linux-x86_64-amd-zen2-1709820180.tar.gz` to S3 bucket succeeded

eessi-bot-aws · 2024-03-07T13:56:22Z

New job on instance eessi-bot-mc-aws for architecture x86_64-amd-zen3 for repository eessi.io-2023.06-software in job dir /project/def-users/SHARED/jobs/2024.03/pr_490/7250

date	job status	comment
Mar 07 13:56:21 UTC 2024	submitted	job id `7250` awaits release by job manager
Mar 07 13:56:35 UTC 2024	released	job awaits launch by Slurm scheduler
Mar 07 14:02:48 UTC 2024	running	job `7250` is running
Mar 07 14:03:56 UTC 2024	finished	😁 SUCCESS (click triangle for details) Details ✅ job output file `slurm-7250.out` ✅ 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-zen3-1709820178.tar.gz` size: 0 MiB (187303 bytes) entries: 4 modules under 2023.06/software/linux/x86_64/amd/zen3/modules/all no module files in tarball software under 2023.06/software/linux/x86_64/amd/zen3/software no software packages in tarball other under 2023.06/software/linux/x86_64/amd/zen3 `.lmod/cache/spiderT.lua` `.lmod/cache/spiderT.luac_5.1` `.lmod/cache/timestamp` `.lmod/lmodrc.lua`
Mar 07 14:03:56 UTC 2024	test result	(no tests yet)
Mar 07 14:08:42 UTC 2024	uploaded	transfer of `eessi-2023.06-software-linux-x86_64-amd-zen3-1709820178.tar.gz` to S3 bucket succeeded

eessi-bot-aws · 2024-03-07T13:56:23Z

New job on instance eessi-bot-mc-aws for architecture aarch64-generic for repository eessi.io-2023.06-software in job dir /project/def-users/SHARED/jobs/2024.03/pr_490/7251

date	job status	comment
Mar 07 13:56:22 UTC 2024	submitted	job id `7251` awaits release by job manager
Mar 07 13:56:28 UTC 2024	released	job awaits launch by Slurm scheduler
Mar 07 14:01:42 UTC 2024	finished	😁 SUCCESS (click triangle for details) Details ✅ job output file `slurm-7251.out` ✅ 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-aarch64-generic-1709820065.tar.gz` size: 0 MiB (185865 bytes) entries: 4 modules under 2023.06/software/linux/aarch64/generic/modules/all no module files in tarball software under 2023.06/software/linux/aarch64/generic/software no software packages in tarball other under 2023.06/software/linux/aarch64/generic `.lmod/cache/spiderT.lua` `.lmod/cache/spiderT.luac_5.1` `.lmod/cache/timestamp` `.lmod/lmodrc.lua`
Mar 07 14:01:42 UTC 2024	test result	(no tests yet)
Mar 07 14:10:19 UTC 2024	uploaded	transfer of `eessi-2023.06-software-linux-aarch64-generic-1709820065.tar.gz` to S3 bucket succeeded

eessi-bot-aws · 2024-03-07T13:56:24Z

New job on instance eessi-bot-mc-aws for architecture aarch64-neoverse_n1 for repository eessi.io-2023.06-software in job dir /project/def-users/SHARED/jobs/2024.03/pr_490/7252

date	job status	comment
Mar 07 13:56:23 UTC 2024	submitted	job id `7252` awaits release by job manager
Mar 07 13:56:30 UTC 2024	released	job awaits launch by Slurm scheduler
Mar 07 14:01:43 UTC 2024	finished	😁 SUCCESS (click triangle for details) Details ✅ job output file `slurm-7252.out` ✅ 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-aarch64-neoverse_n1-1709820067.tar.gz` size: 0 MiB (186005 bytes) entries: 4 modules under 2023.06/software/linux/aarch64/neoverse_n1/modules/all no module files in tarball software under 2023.06/software/linux/aarch64/neoverse_n1/software no software packages in tarball other under 2023.06/software/linux/aarch64/neoverse_n1 `.lmod/cache/spiderT.lua` `.lmod/cache/spiderT.luac_5.1` `.lmod/cache/timestamp` `.lmod/lmodrc.lua`
Mar 07 14:01:43 UTC 2024	test result	(no tests yet)
Mar 07 14:10:38 UTC 2024	uploaded	transfer of `eessi-2023.06-software-linux-aarch64-neoverse_n1-1709820067.tar.gz` to S3 bucket succeeded

eessi-bot-aws · 2024-03-07T13:56:25Z

New job on instance eessi-bot-mc-aws for architecture aarch64-neoverse_v1 for repository eessi.io-2023.06-software in job dir /project/def-users/SHARED/jobs/2024.03/pr_490/7253

date	job status	comment
Mar 07 13:56:24 UTC 2024	submitted	job id `7253` awaits release by job manager
Mar 07 13:56:31 UTC 2024	released	job awaits launch by Slurm scheduler
Mar 07 14:02:51 UTC 2024	finished	😁 SUCCESS (click triangle for details) Details ✅ job output file `slurm-7253.out` ✅ 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-aarch64-neoverse_v1-1709820121.tar.gz` size: 0 MiB (186002 bytes) entries: 4 modules under 2023.06/software/linux/aarch64/neoverse_v1/modules/all no module files in tarball software under 2023.06/software/linux/aarch64/neoverse_v1/software no software packages in tarball other under 2023.06/software/linux/aarch64/neoverse_v1 `.lmod/cache/spiderT.lua` `.lmod/cache/spiderT.luac_5.1` `.lmod/cache/timestamp` `.lmod/lmodrc.lua`
Mar 07 14:02:51 UTC 2024	test result	(no tests yet)
Mar 07 14:10:57 UTC 2024	uploaded	transfer of `eessi-2023.06-software-linux-aarch64-neoverse_v1-1709820121.tar.gz` to S3 bucket succeeded

ocaisa · 2024-03-07T16:10:10Z

All staging PRs merged

casparvl requested a review from ocaisa March 4, 2024 16:01

casparvl marked this pull request as draft March 5, 2024 09:43

casparvl marked this pull request as ready for review March 5, 2024 16:52

Look for site-specific lmodrc file in host_injections. If present, se…

0de249e

…t LMOD_RC

ocaisa requested changes Mar 5, 2024

View reviewed changes

casparvl mentioned this pull request Mar 6, 2024

Hooks should be defined in SitePackage.lua, not in lmodrc.lua #491

Closed

Next the local lmodrc within the versioned directory, e.g. /cvmfs/sof…

c1840dd

…tware.eessi.io/host_injections/2023.06/.lmod/lmodrc.lua

ocaisa reviewed Mar 6, 2024

View reviewed changes

init/eessi_environment_variables Outdated Show resolved Hide resolved

Update init/eessi_environment_variables

df4140a

ocaisa previously approved these changes Mar 6, 2024

View reviewed changes

ocaisa reviewed Mar 6, 2024

View reviewed changes

init/eessi_environment_variables Outdated Show resolved Hide resolved

ocaisa dismissed their stale review via 78e582b March 6, 2024 14:59

Update init/eessi_environment_variables

78e582b

ocaisa reviewed Mar 6, 2024

View reviewed changes

init/eessi_environment_variables Outdated Show resolved Hide resolved

Update init/eessi_environment_variables

77c9723

ocaisa approved these changes Mar 6, 2024

View reviewed changes

init/eessi_environment_variables Outdated Show resolved Hide resolved

ocaisa requested changes Mar 6, 2024

View reviewed changes

Revert changes in eessi_environment_variables. Limit this PR to the b…

e33938f

…ug fix only. We can follow up properly using SitePackage.lua instead

casparvl changed the title ~~Change LMOD RC file setup: use LMOD_CONFIG_DIR instead of LMOD_RC and add namespace prefix to hooks~~ Workaround for LMOD only allowing a single hook to be registered, which made our first hook unused Mar 7, 2024

ocaisa added the bot:deploy Ask bot to deploy missing software installations to EESSI label Mar 7, 2024

ocaisa approved these changes Mar 7, 2024

View reviewed changes

ocaisa merged commit 8dc4d2a into EESSI:2023.06-software.eessi.io Mar 7, 2024
33 checks passed

boegel added the 2023.06-software.eessi.io 2023.06 version of software.eessi.io label Mar 15, 2024

This was referenced Apr 5, 2024

Syncing code-base and CVMFS repository with EESSI (April 2024) NorESSI/software-layer#294

Open

workaround for LMOD to register two hooks NorESSI/software-layer#305

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Workaround for LMOD only allowing a single hook to be registered, which made our first hook unused #490

Workaround for LMOD only allowing a single hook to be registered, which made our first hook unused #490

casparvl commented Mar 4, 2024

eessi-bot-aws bot commented Mar 4, 2024

casparvl commented Mar 5, 2024

casparvl commented Mar 5, 2024 •

edited

Loading

ocaisa commented Mar 5, 2024

casparvl commented Mar 5, 2024

casparvl commented Mar 5, 2024

casparvl commented Mar 5, 2024

ocaisa Mar 5, 2024

casparvl Mar 6, 2024

ocaisa Mar 6, 2024

casparvl commented Mar 6, 2024

casparvl commented Mar 6, 2024

casparvl commented Mar 6, 2024

casparvl commented Mar 6, 2024

ocaisa commented Mar 6, 2024

ocaisa commented Mar 6, 2024

eessi-bot-aws bot commented Mar 6, 2024 •

edited

Loading

eessi-bot-aws bot commented Mar 6, 2024 •

edited

Loading

ocaisa left a comment

ocaisa commented Mar 6, 2024

ocaisa commented Mar 6, 2024

casparvl commented Mar 7, 2024

ocaisa commented Mar 7, 2024

eessi-bot-aws bot commented Mar 7, 2024 •

edited

Loading

eessi-bot-aws bot commented Mar 7, 2024 •

edited

Loading

eessi-bot-aws bot commented Mar 7, 2024 •

edited

Loading

eessi-bot-aws bot commented Mar 7, 2024 •

edited

Loading

eessi-bot-aws bot commented Mar 7, 2024 •

edited

Loading

eessi-bot-aws bot commented Mar 7, 2024 •

edited

Loading

eessi-bot-aws bot commented Mar 7, 2024 •

edited

Loading

eessi-bot-aws bot commented Mar 7, 2024 •

edited

Loading

eessi-bot-aws bot commented Mar 7, 2024 •

edited

Loading

ocaisa commented Mar 7, 2024

Workaround for LMOD only allowing a single hook to be registered, which made our first hook unused #490

Workaround for LMOD only allowing a single hook to be registered, which made our first hook unused #490

Conversation

casparvl commented Mar 4, 2024

eessi-bot-aws bot commented Mar 4, 2024

casparvl commented Mar 5, 2024

casparvl commented Mar 5, 2024 • edited Loading

ocaisa commented Mar 5, 2024

casparvl commented Mar 5, 2024

casparvl commented Mar 5, 2024

casparvl commented Mar 5, 2024

ocaisa Mar 5, 2024

Choose a reason for hiding this comment

casparvl Mar 6, 2024

Choose a reason for hiding this comment

ocaisa Mar 6, 2024

Choose a reason for hiding this comment

casparvl commented Mar 6, 2024

casparvl commented Mar 6, 2024

casparvl commented Mar 6, 2024

casparvl commented Mar 6, 2024

ocaisa commented Mar 6, 2024

ocaisa commented Mar 6, 2024

eessi-bot-aws bot commented Mar 6, 2024 • edited Loading

eessi-bot-aws bot commented Mar 6, 2024 • edited Loading

ocaisa left a comment

Choose a reason for hiding this comment

ocaisa commented Mar 6, 2024

ocaisa commented Mar 6, 2024

casparvl commented Mar 7, 2024

ocaisa commented Mar 7, 2024

eessi-bot-aws bot commented Mar 7, 2024 • edited Loading

eessi-bot-aws bot commented Mar 7, 2024 • edited Loading

eessi-bot-aws bot commented Mar 7, 2024 • edited Loading

eessi-bot-aws bot commented Mar 7, 2024 • edited Loading

eessi-bot-aws bot commented Mar 7, 2024 • edited Loading

eessi-bot-aws bot commented Mar 7, 2024 • edited Loading

eessi-bot-aws bot commented Mar 7, 2024 • edited Loading

eessi-bot-aws bot commented Mar 7, 2024 • edited Loading

eessi-bot-aws bot commented Mar 7, 2024 • edited Loading

ocaisa commented Mar 7, 2024

casparvl commented Mar 5, 2024 •

edited

Loading

eessi-bot-aws bot commented Mar 6, 2024 •

edited

Loading

eessi-bot-aws bot commented Mar 6, 2024 •

edited

Loading

eessi-bot-aws bot commented Mar 7, 2024 •

edited

Loading

eessi-bot-aws bot commented Mar 7, 2024 •

edited

Loading

eessi-bot-aws bot commented Mar 7, 2024 •

edited

Loading

eessi-bot-aws bot commented Mar 7, 2024 •

edited

Loading

eessi-bot-aws bot commented Mar 7, 2024 •

edited

Loading

eessi-bot-aws bot commented Mar 7, 2024 •

edited

Loading

eessi-bot-aws bot commented Mar 7, 2024 •

edited

Loading

eessi-bot-aws bot commented Mar 7, 2024 •

edited

Loading

eessi-bot-aws bot commented Mar 7, 2024 •

edited

Loading