{2023.06}[2023a] Rivet 3.1.9 #418

APN-Pucky · 2023-12-06T08:56:25Z

No description provided.

eessi-bot · 2023-12-06T08:56:29Z

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

trz42 · 2023-12-06T11:58:47Z

Thanks for the PR @APN-Pucky . I retargeted the PR to 2023.06-software.eessi.io. In that branch/version of the software stack we currently have foss/2023a (GCC/12.3.0) available. Soon, there should be foss/2022b (GCC/12.2.0) too.

Could you try to use either of these?

You would need to use a different easyconfig file (if it is not available yet via EasyBuild v4.8.2, you would need to open a pull request for a new/updated easyconfig file to the easybuilders/easyconfigs repository first, apologies for the extra work)
You would have to move the easyconfig from eessi-2023.06-eb-4.7.2-2022a.yml to either easystacks/software.eessi.io/2023.06/eessi-2023.06-eb-4.8.2-2023a.yml or easystacks/software.eessi.io/2023.06/eessi-2023.06-eb-4.8.2-2022b.yml

Please let us know if you struggle with any of these changes / additional work (PR for easyconfig).

APN-Pucky · 2023-12-06T14:26:14Z

Since this will also require updates of Rivets dependencies should they all in one PR to easyconfigs or single per-package requests?

eessi-bot · 2023-12-06T14:26:17Z

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

account APN-Pucky has NO permission to send commands to the bot

trz42 · 2023-12-06T16:35:19Z

Since this will also require updates of Rivets dependencies should they all in one PR to easyconfigs or single per-package requests?

They should go in one PR I think. Otherwise you would have to list the dependencies in the easystack file and add the option from-pr: for each easyconfig you have opened a PR.

boegel · 2024-01-16T10:42:31Z

@APN-Pucky Are you planning to follow up on this?

APN-Pucky · 2024-01-16T10:44:55Z

@APN-Pucky Are you planning to follow up on this?

Yes, but I thought when I am already at it I'd update all the dependencies in the 2023a for easybuild too.

eessi-bot · 2024-01-16T10:44:58Z

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

account APN-Pucky has NO permission to send commands to the bot

APN-Pucky · 2024-01-22T11:56:20Z

The easyconfigs MR is merged now. Can the build bot please be triggered?

eessi-bot · 2024-01-22T11:56:23Z

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

account APN-Pucky has NO permission to send commands to the bot

casparvl · 2024-01-22T12:12:23Z

bot: build repo:eessi.io-2023.06-software arch:x86_64/intel/haswell

eessi-bot · 2024-01-22T12:12:25Z

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/intel/haswell from casparvl
- expanded format: build repository:eessi.io-2023.06-software architecture:x86_64/intel/haswell
handling command build repository:eessi.io-2023.06-software architecture:x86_64/intel/haswell resulted in:
- submitted job 4568, for details & status see {2023.06}[2023a] Rivet 3.1.9 #418 (comment)

eessi-bot · 2024-01-22T12:12:29Z

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.01/pr_418/4568

date	job status	comment
Jan 22 12:12:28 UTC 2024	submitted	job id `4568` awaits release by job manager
Jan 22 12:13:17 UTC 2024	released	job awaits launch by Slurm scheduler
Jan 22 12:18:19 UTC 2024	running	job `4568` is running
Jan 22 12:28:30 UTC 2024	finished	😢 FAILURE (click triangle for details) Details ✅ job output file `slurm-4568.out` ❌ found message matching `ERROR:` ❌ found message matching `FAILED:` ❌ found message matching `required modules missing:` ❌ no message matching `No missing installations` ✅ found message matching `.tar.gz created!` Artefacts No artefacts were created or found.
Jan 22 12:28:30 UTC 2024	test result	(no tests yet)

APN-Pucky · 2024-01-22T16:12:55Z

What does that mean?

eessi-bot · 2024-01-22T16:12:59Z

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

account APN-Pucky has NO permission to send commands to the bot

casparvl · 2024-01-22T16:31:58Z

It means there was some error during the build. I'll have to go into the system that builds things to find the error.

Note however that another way to debug is to rerun the build yourself, manually, according to the instructions on https://www.eessi.io/docs/adding_software/debugging_failed_builds/ . This should mimic exactly what our bot does, and thus should result in the same build failure. Ideally, that lets you debug the issue on your own system, which is much easier :)

For now, I'll go into our build system and check if the error is maybe trivial... I'll paste it here in a minute

casparvl · 2024-01-22T16:34:12Z

checking for zlib.h... no
configure: error: either specify a valid zlib installation with --with-zlib=DIR or disable zlib usage with --without-zlib

That's... weird to say the least, since I'm assuming that zlib is listed somewhere as a dependency (directly or indirectly) for Rivet...

Edit: correction, it was trying to build YODA when it threw this error. So that's the EasyConfig we should check, I guess.

casparvl · 2024-01-22T16:45:10Z

Note that some issues may pop up in our builds that you might not have seen before since we build in a very minimal container. Thus, where some EasyConfigs might succesfully build because they silently pick up on system dependencies, they would fail in this minimal container. It's actually a very good test to figure out if all dependencies have been listed correctly.

In YODA's case, they haven't. This configure tells me YODA (at least in the configuration as provided by this EasyConfig) depends on zlib, but that is not listed in the dependencies. So, step 1 would be to add that.

However, in this particular case, it won't resolve the issue: in EESSI, we filter zlib as a dependency, as we want to be able to do security updates to zlib. Thus, this package should pick up on the zlib from our compatibility layer, which we can apply security patches to if needed. However, clearly, the configure fails to find it. My bet is, it fails to find it, because it is in a non-standard location (e.g. /cvmfs/software.eessi.io/versions/2023.06/compat/linux/x86_64/usr/include/zlib.h for x86_64 architectures). I need to think how to best resolve this. I'm actually quite surprised we haven't hit this with other packages - zlib is a very common dependency. Maybe this configure somehow uses a different mechanism of finding zlib then most others...? I'll check with some other people in EESSI for ideas.

Note, unrelated to it's installation in EESSI: it's still a good idea to add zlib as dependency to the YODA EasyConfig. It'll guarantee that it uses the zlib provided by EasyBuild when people install YODA with EasyBuild, instead of a system-version.

APN-Pucky · 2024-01-22T17:07:10Z

Thanks, I'll update the YODA easyconfigs.

eessi-bot · 2024-01-22T17:07:13Z

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

account APN-Pucky has NO permission to send commands to the bot

APN-Pucky · 2024-01-22T21:59:11Z

Maybe this configure somehow uses a different mechanism of finding zlib then most others...?

I updated the zlib dependency here: easybuilders/easybuild-easyconfigs#19679
How does the zlib dependency replacement work? Above MR also adds a previously unused --with-zlib=$EBROOTZLIB configopt. If EESSI just replaces that variable, this might fix it.

eessi-bot · 2024-01-22T21:59:13Z

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

account APN-Pucky has NO permission to send commands to the bot

casparvl · 2024-01-23T16:13:44Z

Yes, but with the new MR, where I added the --with-zlib=$EBROOTZLIB which resulted in the error of using -with-zlib= without a parameter as you said.

Ah yeah, I used the old MR to reproduce the issue.

The problem here is -I/usr/include, right?

Yes, this is the problem:

{EESSI 2023.06} Apptainer> gcc -c -O2 -ftree-vectorize -march=native -fno-math-errno -fPIC -I/cvmfs/software.eessi.io/versions/2023.06/software/linux/x86_64/amd/zen2/software/Python/3.11.3-GCCcore-12.3.0/include -I/usr/include conftest.c
In file included from conftest.c:31:
/usr/include/stdio.h:781:10: fatal error: bits/sys_errlist.h: No such file or directory
  781 | #include <bits/sys_errlist.h>
      |          ^~~~~~~~~~~~~~~~~~~~
compilation terminated.
{EESSI 2023.06} Apptainer> gcc -c -O2 -ftree-vectorize -march=native -fno-math-errno -fPIC -I/cvmfs/software.eessi.io/versions/2023.06/software/linux/x86_64/amd/zen2/software/Python/3.11.3-GCCcore-12.3.0/include conftest.c
{EESSI 2023.06} Apptainer>

I think you haven't seen this on other systems because that bits/sys_errlist.h header gets picked up succesfully there. However, in our container, that particular header is in /usr/include/x86_64-linux-gnu/bits/sys_errlist.h

casparvl · 2024-01-23T16:14:58Z

As for the solution... I'd really be interested what triggers to configure to add this -I/usr/include and to get rid of it... The fact that you don't want to pick up anything from the host (e.g. from /usr/include) is more general in EasyBuild. It's just that our container-build setup exposed the issue...

casparvl · 2024-01-23T16:18:04Z

Uhg, it has this very ugly section in the configure...

## Optional zlib support for gzip-compressed data streams/files
#
# Handle user hints
#
{ printf "%s\n" "$as_me:${as_lineno-$LINENO}: checking if zlib is wanted" >&5
printf %s "checking if zlib is wanted... " >&6; }
zlib_places="/usr/local /usr /opt/local /sw"

# Check whether --with-zlib was given.
if test ${with_zlib+y}
then :
  withval=$with_zlib; if test "$withval" != no ; then
  { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: yes" >&5
printf "%s\n" "yes" >&6; }
  if test -d "$withval"
  then
    zlib_places="$withval $zlib_places"
  else
    { printf "%s\n" "$as_me:${as_lineno-$LINENO}: WARNING: Sorry, $withval does not exist, checking usual places" >&5
printf "%s\n" "$as_me: WARNING: Sorry, $withval does not exist, checking usual places" >&2;}
  fi
else
  zlib_places=
  { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: no" >&5
printf "%s\n" "no" >&6; }
fi
else $as_nop
  { printf "%s\n" "$as_me:${as_lineno-$LINENO}: result: yes" >&5
printf "%s\n" "yes" >&6; }
fi


#
# Locate zlib, if wanted
#
if test -n "${zlib_places}"
then
        # check the user supplied or any other more or less 'standard' place:
        #   Most UNIX systems      : /usr/local and /usr
        #   MacPorts / Fink on OSX : /opt/local respectively /sw
        for ZLIB_HOME in ${zlib_places} ; do
          if test -f "${ZLIB_HOME}/include/zlib.h"; then break; fi
          ZLIB_HOME=""
        done

  ZLIB_OLD_LDFLAGS=$LDFLAGS
  ZLIB_OLD_CPPFLAGS=$CPPFLAGS
  if test -n "${ZLIB_HOME}"; then
        LDFLAGS="$LDFLAGS -L${ZLIB_HOME}/lib"
        CPPFLAGS="$CPPFLAGS -I${ZLIB_HOME}/include"
  fi

Clearly, that for ZLIB_HOME loop is looping over system directories, and then locating the system zlib (instead of the one provided by EasyBuild or the one from the compatiblity layer - as we would want in EESSI).

casparvl · 2024-01-23T16:19:47Z

It originally comes from here btw:

cat m4/ax_check_zlib.m4 | grep zlib_places
zlib_places="/usr/local /usr /opt/local /sw"
    zlib_places="$withval $zlib_places"
  zlib_places=
if test -n "${zlib_places}"
        for ZLIB_HOME in ${zlib_places} ; do

casparvl · 2024-01-23T16:29:54Z

Apparently, it is the officially documented behaviour for ax_check_zlib, even if we might not like it from an EasyBuild perspective... https://www.gnu.org/software/autoconf-archive/ax_check_zlib.html

I see two potential approaches:

Change the ax_check_zlib.m4 so that it finds the right zlib. For standard EB, that would mean: the zlib listed as dependency. For anyone having zlib in the filter-deps (like EESSI), it would mean using %(sysroot)s/include.
Pass --with-zlib and as argument, use $EBROOTZLIB/include (if zlib is not in filter-deps) or use %(sysroot)s/include if it is.

Now, since this involves logic (namely, checking an EasyBuild option, doing one thing in one case, and another thing in another case), it has to be done at an EasyBlock level, regardless of whether we go for option 1 or 2. Personally, I think 2 would be the cleanest approach.

It shouldn't be rocket science to implement it, but still a bit of work. Before you go through that, I'd like to at least get one more opinion from one of the EESSI support people... I'll reach out to them on Slack, see if I can get some input on this :)

boegel · 2024-01-23T20:08:10Z

I'm not sure it's true that this requires logic and hence an easyblock. How about this construct (use %(sysroot)s template to define a fallback value in case $EBROOTZLIB is not defined:

configopts = "--with-zlib=${EBROOTZLIB:-%(sysroot)s}/include "

APN-Pucky · 2024-01-23T21:21:46Z

That's smart. The fallback mode seems to work in my build on top of EESSI and in the debug container. I updated the PR reference in this PR.

eessi-bot · 2024-01-23T21:21:49Z

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

account APN-Pucky has NO permission to send commands to the bot

casparvl · 2024-01-24T09:44:17Z

Great idea from @boegel and much simpler. I knew I was asking for a second pair of eyes for a good reason ;-)

I'll kick off another bot build.

Just in case we wonder about this in the future: I saw that your --with-zlib was slightly different from what Kenneth suggested, namely

--with-zlib=${EBROOTZLIB:-%(sysroot)s/usr}

But indeed from the docs of ax_check_zlib.m4 that should be correct:

If the –with-zlib=DIR is specified, it will try to find it in DIR/include/zlib.h and DIR/lib/libz.a.

casparvl · 2024-01-24T09:45:04Z

bot: build repo:eessi.io-2023.06-software arch:x86_64/intel/haswell

eessi-bot · 2024-01-24T09:45:06Z

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/intel/haswell from casparvl
- expanded format: build repository:eessi.io-2023.06-software architecture:x86_64/intel/haswell
handling command build repository:eessi.io-2023.06-software architecture:x86_64/intel/haswell resulted in:
- submitted job 4687, for details & status see {2023.06}[2023a] Rivet 3.1.9 #418 (comment)

eessi-bot · 2024-01-24T09:45:14Z

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.01/pr_418/4687

date	job status	comment
Jan 24 09:45:13 UTC 2024	submitted	job id `4687` awaits release by job manager
Jan 24 09:45:45 UTC 2024	released	job awaits launch by Slurm scheduler
Jan 24 09:50:55 UTC 2024	running	job `4687` is running
Jan 24 10:12:46 UTC 2024	finished	😁 SUCCESS (click triangle for details) Details ✅ job output file `slurm-4687.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-1706091075.tar.gz` size: 87 MiB (92008705 bytes) entries: 7602 modules under 2023.06/software/linux/x86_64/intel/haswell/modules/all `fastjet/3.4.2-gompi-2023a.lua` `fastjet-contrib/1.053-gompi-2023a.lua` `HepMC3/3.2.6-GCC-12.3.0.lua` `Rivet/3.1.9-gompi-2023a-HepMC3-3.2.6.lua` `siscone/3.0.6-GCCcore-12.3.0.lua` `YODA/1.9.9-GCC-12.3.0.lua` software under 2023.06/software/linux/x86_64/intel/haswell/software `fastjet/3.4.2-gompi-2023a` `fastjet-contrib/1.053-gompi-2023a` `HepMC3/3.2.6-GCC-12.3.0` `Rivet/3.1.9-gompi-2023a-HepMC3-3.2.6` `siscone/3.0.6-GCCcore-12.3.0` `YODA/1.9.9-GCC-12.3.0` other under 2023.06/software/linux/x86_64/intel/haswell `.lmod/cache/spiderT.lua` `.lmod/cache/spiderT.luac_5.1` `.lmod/cache/timestamp`
Jan 24 10:12:46 UTC 2024	test result	(no tests yet)
Jan 24 20:43:59 UTC 2024	uploaded	transfer of `eessi-2023.06-software-linux-x86_64-intel-haswell-1706091075.tar.gz` to S3 bucket succeeded

casparvl · 2024-01-24T11:36:18Z

bot: build repo:eessi.io-2023.06-software arch:x86_64/generic
bot: build repo:eessi.io-2023.06-software arch:x86_64/intel/skylake_avx512
bot: build repo:eessi.io-2023.06-software arch:x86_64/amd/zen2
bot: build repo:eessi.io-2023.06-software arch:x86_64/amd/zen3
bot: build repo:eessi.io-2023.06-software arch:aarch64/generic
bot: build repo:eessi.io-2023.06-software arch:aarch64/neoverse_n1
bot: build repo:eessi.io-2023.06-software arch:aarch64/neoverse_v1

eessi-bot · 2024-01-24T11:36:22Z

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/generic from casparvl
- expanded format: build repository:eessi.io-2023.06-software architecture:x86_64/generic
received bot command build repo:eessi.io-2023.06-software arch:x86_64/intel/skylake_avx512 from casparvl
- expanded format: build repository:eessi.io-2023.06-software architecture:x86_64/intel/skylake_avx512
received bot command build repo:eessi.io-2023.06-software arch:x86_64/amd/zen2 from casparvl
- expanded format: build repository:eessi.io-2023.06-software architecture:x86_64/amd/zen2
received bot command build repo:eessi.io-2023.06-software arch:x86_64/amd/zen3 from casparvl
- expanded format: build repository:eessi.io-2023.06-software architecture:x86_64/amd/zen3
received bot command build repo:eessi.io-2023.06-software arch:aarch64/generic from casparvl
- expanded format: build repository:eessi.io-2023.06-software architecture:aarch64/generic
received bot command build repo:eessi.io-2023.06-software arch:aarch64/neoverse_n1 from casparvl
- expanded format: build repository:eessi.io-2023.06-software architecture:aarch64/neoverse_n1
received bot command build repo:eessi.io-2023.06-software arch:aarch64/neoverse_v1 from casparvl
- expanded format: build repository:eessi.io-2023.06-software architecture:aarch64/neoverse_v1
handling command build repository:eessi.io-2023.06-software architecture:x86_64/generic resulted in:
- submitted job 4688, for details & status see {2023.06}[2023a] Rivet 3.1.9 #418 (comment)
handling command build repository:eessi.io-2023.06-software architecture:x86_64/intel/skylake_avx512 resulted in:
- submitted job 4689, for details & status see {2023.06}[2023a] Rivet 3.1.9 #418 (comment)
handling command build repository:eessi.io-2023.06-software architecture:x86_64/amd/zen2 resulted in:
- submitted job 4690, for details & status see {2023.06}[2023a] Rivet 3.1.9 #418 (comment)
handling command build repository:eessi.io-2023.06-software architecture:x86_64/amd/zen3 resulted in:
- submitted job 4691, for details & status see {2023.06}[2023a] Rivet 3.1.9 #418 (comment)
handling command build repository:eessi.io-2023.06-software architecture:aarch64/generic resulted in:
- submitted job 4692, for details & status see {2023.06}[2023a] Rivet 3.1.9 #418 (comment)
handling command build repository:eessi.io-2023.06-software architecture:aarch64/neoverse_n1 resulted in:
- submitted job 4693, for details & status see {2023.06}[2023a] Rivet 3.1.9 #418 (comment)
handling command build repository:eessi.io-2023.06-software architecture:aarch64/neoverse_v1 resulted in:
- submitted job 4694, for details & status see {2023.06}[2023a] Rivet 3.1.9 #418 (comment)

eessi-bot · 2024-01-24T11:36:26Z

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.01/pr_418/4688

date	job status	comment
Jan 24 11:36:25 UTC 2024	submitted	job id `4688` awaits release by job manager
Jan 24 11:37:27 UTC 2024	released	job awaits launch by Slurm scheduler
Jan 24 12:46:01 UTC 2024	running	job `4688` is running
Jan 24 13:05:48 UTC 2024	finished	😁 SUCCESS (click triangle for details) Details ✅ job output file `slurm-4688.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-1706101500.tar.gz` size: 87 MiB (91376361 bytes) entries: 7602 modules under 2023.06/software/linux/x86_64/generic/modules/all `fastjet/3.4.2-gompi-2023a.lua` `fastjet-contrib/1.053-gompi-2023a.lua` `HepMC3/3.2.6-GCC-12.3.0.lua` `Rivet/3.1.9-gompi-2023a-HepMC3-3.2.6.lua` `siscone/3.0.6-GCCcore-12.3.0.lua` `YODA/1.9.9-GCC-12.3.0.lua` software under 2023.06/software/linux/x86_64/generic/software `fastjet/3.4.2-gompi-2023a` `fastjet-contrib/1.053-gompi-2023a` `HepMC3/3.2.6-GCC-12.3.0` `Rivet/3.1.9-gompi-2023a-HepMC3-3.2.6` `siscone/3.0.6-GCCcore-12.3.0` `YODA/1.9.9-GCC-12.3.0` other under 2023.06/software/linux/x86_64/generic `.lmod/cache/spiderT.lua` `.lmod/cache/spiderT.luac_5.1` `.lmod/cache/timestamp`
Jan 24 13:05:48 UTC 2024	test result	(no tests yet)
Jan 24 20:44:20 UTC 2024	uploaded	transfer of `eessi-2023.06-software-linux-x86_64-generic-1706101500.tar.gz` to S3 bucket succeeded

eessi-bot · 2024-01-24T11:36:31Z

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.01/pr_418/4689

date	job status	comment
Jan 24 11:36:30 UTC 2024	submitted	job id `4689` awaits release by job manager
Jan 24 11:37:30 UTC 2024	released	job awaits launch by Slurm scheduler
Jan 24 11:45:00 UTC 2024	running	job `4689` is running
Jan 24 12:02:13 UTC 2024	finished	😁 SUCCESS (click triangle for details) Details ✅ job output file `slurm-4689.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-1706097676.tar.gz` size: 87 MiB (91901902 bytes) entries: 7602 modules under 2023.06/software/linux/x86_64/intel/skylake_avx512/modules/all `fastjet/3.4.2-gompi-2023a.lua` `fastjet-contrib/1.053-gompi-2023a.lua` `HepMC3/3.2.6-GCC-12.3.0.lua` `Rivet/3.1.9-gompi-2023a-HepMC3-3.2.6.lua` `siscone/3.0.6-GCCcore-12.3.0.lua` `YODA/1.9.9-GCC-12.3.0.lua` software under 2023.06/software/linux/x86_64/intel/skylake_avx512/software `fastjet/3.4.2-gompi-2023a` `fastjet-contrib/1.053-gompi-2023a` `HepMC3/3.2.6-GCC-12.3.0` `Rivet/3.1.9-gompi-2023a-HepMC3-3.2.6` `siscone/3.0.6-GCCcore-12.3.0` `YODA/1.9.9-GCC-12.3.0` other under 2023.06/software/linux/x86_64/intel/skylake_avx512 `.lmod/cache/spiderT.lua` `.lmod/cache/spiderT.luac_5.1` `.lmod/cache/timestamp`
Jan 24 12:02:13 UTC 2024	test result	(no tests yet)
Jan 24 20:44:41 UTC 2024	uploaded	transfer of `eessi-2023.06-software-linux-x86_64-intel-skylake_avx512-1706097676.tar.gz` to S3 bucket succeeded

eessi-bot · 2024-01-24T11:36:35Z

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.01/pr_418/4690

date	job status	comment
Jan 24 11:36:34 UTC 2024	submitted	job id `4690` awaits release by job manager
Jan 24 11:37:23 UTC 2024	released	job awaits launch by Slurm scheduler
Jan 24 11:43:49 UTC 2024	running	job `4690` is running
Jan 24 12:02:11 UTC 2024	finished	😁 SUCCESS (click triangle for details) Details ✅ job output file `slurm-4690.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-1706097637.tar.gz` size: 87 MiB (92001866 bytes) entries: 7602 modules under 2023.06/software/linux/x86_64/amd/zen2/modules/all `fastjet/3.4.2-gompi-2023a.lua` `fastjet-contrib/1.053-gompi-2023a.lua` `HepMC3/3.2.6-GCC-12.3.0.lua` `Rivet/3.1.9-gompi-2023a-HepMC3-3.2.6.lua` `siscone/3.0.6-GCCcore-12.3.0.lua` `YODA/1.9.9-GCC-12.3.0.lua` software under 2023.06/software/linux/x86_64/amd/zen2/software `fastjet/3.4.2-gompi-2023a` `fastjet-contrib/1.053-gompi-2023a` `HepMC3/3.2.6-GCC-12.3.0` `Rivet/3.1.9-gompi-2023a-HepMC3-3.2.6` `siscone/3.0.6-GCCcore-12.3.0` `YODA/1.9.9-GCC-12.3.0` other under 2023.06/software/linux/x86_64/amd/zen2 `.lmod/cache/spiderT.lua` `.lmod/cache/spiderT.luac_5.1` `.lmod/cache/timestamp`
Jan 24 12:02:11 UTC 2024	test result	(no tests yet)
Jan 24 20:45:02 UTC 2024	uploaded	transfer of `eessi-2023.06-software-linux-x86_64-amd-zen2-1706097637.tar.gz` to S3 bucket succeeded

eessi-bot · 2024-01-24T11:36:39Z

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.01/pr_418/4691

date	job status	comment
Jan 24 11:36:38 UTC 2024	submitted	job id `4691` awaits release by job manager
Jan 24 11:37:25 UTC 2024	released	job awaits launch by Slurm scheduler
Jan 24 11:43:52 UTC 2024	running	job `4691` is running
Jan 24 11:59:59 UTC 2024	finished	😁 SUCCESS (click triangle for details) Details ✅ job output file `slurm-4691.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-1706097500.tar.gz` size: 87 MiB (91989234 bytes) entries: 7602 modules under 2023.06/software/linux/x86_64/amd/zen3/modules/all `fastjet/3.4.2-gompi-2023a.lua` `fastjet-contrib/1.053-gompi-2023a.lua` `HepMC3/3.2.6-GCC-12.3.0.lua` `Rivet/3.1.9-gompi-2023a-HepMC3-3.2.6.lua` `siscone/3.0.6-GCCcore-12.3.0.lua` `YODA/1.9.9-GCC-12.3.0.lua` software under 2023.06/software/linux/x86_64/amd/zen3/software `fastjet/3.4.2-gompi-2023a` `fastjet-contrib/1.053-gompi-2023a` `HepMC3/3.2.6-GCC-12.3.0` `Rivet/3.1.9-gompi-2023a-HepMC3-3.2.6` `siscone/3.0.6-GCCcore-12.3.0` `YODA/1.9.9-GCC-12.3.0` other under 2023.06/software/linux/x86_64/amd/zen3 `.lmod/cache/spiderT.lua` `.lmod/cache/spiderT.luac_5.1` `.lmod/cache/timestamp`
Jan 24 11:59:59 UTC 2024	test result	(no tests yet)
Jan 24 20:45:22 UTC 2024	uploaded	transfer of `eessi-2023.06-software-linux-x86_64-amd-zen3-1706097500.tar.gz` to S3 bucket succeeded

eessi-bot · 2024-01-24T11:36:43Z

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.01/pr_418/4692

date	job status	comment
Jan 24 11:36:42 UTC 2024	submitted	job id `4692` awaits release by job manager
Jan 24 11:37:18 UTC 2024	released	job awaits launch by Slurm scheduler
Jan 24 11:42:41 UTC 2024	running	job `4692` is running
Jan 24 12:01:05 UTC 2024	finished	😁 SUCCESS (click triangle for details) Details ✅ job output file `slurm-4692.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-1706097584.tar.gz` size: 85 MiB (89458552 bytes) entries: 7602 modules under 2023.06/software/linux/aarch64/generic/modules/all `fastjet/3.4.2-gompi-2023a.lua` `fastjet-contrib/1.053-gompi-2023a.lua` `HepMC3/3.2.6-GCC-12.3.0.lua` `Rivet/3.1.9-gompi-2023a-HepMC3-3.2.6.lua` `siscone/3.0.6-GCCcore-12.3.0.lua` `YODA/1.9.9-GCC-12.3.0.lua` software under 2023.06/software/linux/aarch64/generic/software `fastjet/3.4.2-gompi-2023a` `fastjet-contrib/1.053-gompi-2023a` `HepMC3/3.2.6-GCC-12.3.0` `Rivet/3.1.9-gompi-2023a-HepMC3-3.2.6` `siscone/3.0.6-GCCcore-12.3.0` `YODA/1.9.9-GCC-12.3.0` other under 2023.06/software/linux/aarch64/generic `.lmod/cache/spiderT.lua` `.lmod/cache/spiderT.luac_5.1` `.lmod/cache/timestamp`
Jan 24 12:01:05 UTC 2024	test result	(no tests yet)
Jan 24 20:45:43 UTC 2024	uploaded	transfer of `eessi-2023.06-software-linux-aarch64-generic-1706097584.tar.gz` to S3 bucket succeeded

eessi-bot · 2024-01-24T11:36:47Z

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.01/pr_418/4693

date	job status	comment
Jan 24 11:36:46 UTC 2024	submitted	job id `4693` awaits release by job manager
Jan 24 11:37:21 UTC 2024	released	job awaits launch by Slurm scheduler
Jan 24 11:42:43 UTC 2024	running	job `4693` is running
Jan 24 12:01:06 UTC 2024	finished	😁 SUCCESS (click triangle for details) Details ✅ job output file `slurm-4693.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-1706097569.tar.gz` size: 85 MiB (89304266 bytes) entries: 7602 modules under 2023.06/software/linux/aarch64/neoverse_n1/modules/all `fastjet/3.4.2-gompi-2023a.lua` `fastjet-contrib/1.053-gompi-2023a.lua` `HepMC3/3.2.6-GCC-12.3.0.lua` `Rivet/3.1.9-gompi-2023a-HepMC3-3.2.6.lua` `siscone/3.0.6-GCCcore-12.3.0.lua` `YODA/1.9.9-GCC-12.3.0.lua` software under 2023.06/software/linux/aarch64/neoverse_n1/software `fastjet/3.4.2-gompi-2023a` `fastjet-contrib/1.053-gompi-2023a` `HepMC3/3.2.6-GCC-12.3.0` `Rivet/3.1.9-gompi-2023a-HepMC3-3.2.6` `siscone/3.0.6-GCCcore-12.3.0` `YODA/1.9.9-GCC-12.3.0` other under 2023.06/software/linux/aarch64/neoverse_n1 `.lmod/cache/spiderT.lua` `.lmod/cache/spiderT.luac_5.1` `.lmod/cache/timestamp`
Jan 24 12:01:06 UTC 2024	test result	(no tests yet)
Jan 24 20:46:04 UTC 2024	uploaded	transfer of `eessi-2023.06-software-linux-aarch64-neoverse_n1-1706097569.tar.gz` to S3 bucket succeeded

eessi-bot · 2024-01-24T11:37:30Z

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.01/pr_418/4694

date	job status	comment
Jan 24 11:37:29 UTC 2024	submitted	job id `4694` awaits release by job manager
Jan 24 11:38:33 UTC 2024	released	job awaits launch by Slurm scheduler
Jan 24 11:46:06 UTC 2024	running	job `4694` is running
Jan 24 12:01:08 UTC 2024	finished	😁 SUCCESS (click triangle for details) Details ✅ job output file `slurm-4694.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-1706097575.tar.gz` size: 85 MiB (89317305 bytes) entries: 7602 modules under 2023.06/software/linux/aarch64/neoverse_v1/modules/all `fastjet/3.4.2-gompi-2023a.lua` `fastjet-contrib/1.053-gompi-2023a.lua` `HepMC3/3.2.6-GCC-12.3.0.lua` `Rivet/3.1.9-gompi-2023a-HepMC3-3.2.6.lua` `siscone/3.0.6-GCCcore-12.3.0.lua` `YODA/1.9.9-GCC-12.3.0.lua` software under 2023.06/software/linux/aarch64/neoverse_v1/software `fastjet/3.4.2-gompi-2023a` `fastjet-contrib/1.053-gompi-2023a` `HepMC3/3.2.6-GCC-12.3.0` `Rivet/3.1.9-gompi-2023a-HepMC3-3.2.6` `siscone/3.0.6-GCCcore-12.3.0` `YODA/1.9.9-GCC-12.3.0` other under 2023.06/software/linux/aarch64/neoverse_v1 `.lmod/cache/spiderT.lua` `.lmod/cache/spiderT.luac_5.1` `.lmod/cache/timestamp`
Jan 24 12:01:08 UTC 2024	test result	(no tests yet)
Jan 24 20:46:25 UTC 2024	uploaded	transfer of `eessi-2023.06-software-linux-aarch64-neoverse_v1-1706097575.tar.gz` to S3 bucket succeeded

casparvl · 2024-01-24T16:23:47Z

Just FYI: I'd like to merge easybuilders/easybuild-easyconfigs#19679 so we can be sure that's the final version before we deploy these builds in EESSI. I'm waiting on one more test report from a build I'm running, if that's ok, I think we can merge there and deploy here. I might be able to find a few minutes tonight to do that... otherwise it'll be tomorrow.

APN-Pucky · 2024-01-24T19:44:58Z

Thanks for getting this through despite the hurdles!

eessi-bot · 2024-01-24T19:45:01Z

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

account APN-Pucky has NO permission to send commands to the bot

casparvl · 2024-01-24T20:45:13Z

Thanks for getting this through despite the hurdles!

Sure! Thank you for pushing through :) As you've noticed, we are definitely still building experience with the particularities of the EESSI setup, but things go more and more smoothly as we learn :)

casparvl

Lgtm!

…20.0-foss/2023a {2023.06}[foss/2023a] phonopy V2.20.0

trz42 added the 2023.06-software.eessi.io 2023.06 version of software.eessi.io label Dec 6, 2023

trz42 changed the base branch from 2023.06 to 2023.06-software.eessi.io December 6, 2023 11:58

boegel changed the title ~~adding Rivet 3.1.7 with GCC/11.3.0 to EESSI 2023.06~~ {2023.06}[2022a] Rivet 3.1.7 Jan 11, 2024

APN-Pucky mentioned this pull request Jan 18, 2024

{phys}[gompi/2023a] Rivet v3.1.9, HepMC3 v3.2.6, fastjet v3.4.2, fastjet-contrib v1.053, siscone v3.0.6 easybuilders/easybuild-easyconfigs#19631

Merged

{2023.06}[2023a] Rivet 3.1.9

13ea5e7

APN-Pucky force-pushed the rivet branch from aa7501f to 13ea5e7 Compare January 18, 2024 12:31

APN-Pucky changed the title ~~{2023.06}[2022a] Rivet 3.1.7~~ {2023.06}[2023a] Rivet 3.1.9 Jan 18, 2024

APN-Pucky mentioned this pull request Jan 22, 2024

Add zlib dependency to YODA and Rivet easybuilders/easybuild-easyconfigs#19679

Merged

Use MR with fixed zlib

97572ac

casparvl added the bot:deploy Ask bot to deploy missing software installations to EESSI label Jan 24, 2024

casparvl approved these changes Jan 24, 2024

View reviewed changes

casparvl merged commit 0754b62 into EESSI:2023.06-software.eessi.io Jan 24, 2024
33 checks passed

TopRichard added a commit to TopRichard/bot-software-layer1 that referenced this pull request Jul 11, 2024

Merge pull request EESSI#418 from TopRichard/nessi-2023.06-phonopy/2.…

5085e15

…20.0-foss/2023a {2023.06}[foss/2023a] phonopy V2.20.0

{2023.06}[2023a] Rivet 3.1.9 #418

{2023.06}[2023a] Rivet 3.1.9 #418

Conversation

APN-Pucky commented Dec 6, 2023

eessi-bot bot commented Dec 6, 2023

trz42 commented Dec 6, 2023

APN-Pucky commented Dec 6, 2023

eessi-bot bot commented Dec 6, 2023

trz42 commented Dec 6, 2023

boegel commented Jan 16, 2024

APN-Pucky commented Jan 16, 2024

eessi-bot bot commented Jan 16, 2024

APN-Pucky commented Jan 22, 2024

eessi-bot bot commented Jan 22, 2024

casparvl commented Jan 22, 2024

eessi-bot bot commented Jan 22, 2024 • edited Loading

eessi-bot bot commented Jan 22, 2024 • edited Loading

APN-Pucky commented Jan 22, 2024

eessi-bot bot commented Jan 22, 2024

casparvl commented Jan 22, 2024

casparvl commented Jan 22, 2024 • edited Loading

casparvl commented Jan 22, 2024

APN-Pucky commented Jan 22, 2024

eessi-bot bot commented Jan 22, 2024

APN-Pucky commented Jan 22, 2024

eessi-bot bot commented Jan 22, 2024

casparvl commented Jan 23, 2024

casparvl commented Jan 23, 2024

casparvl commented Jan 23, 2024

casparvl commented Jan 23, 2024

casparvl commented Jan 23, 2024

boegel commented Jan 23, 2024

APN-Pucky commented Jan 23, 2024

eessi-bot bot commented Jan 23, 2024

casparvl commented Jan 24, 2024

casparvl commented Jan 24, 2024

eessi-bot bot commented Jan 24, 2024 • edited Loading

eessi-bot bot commented Jan 24, 2024 • edited Loading

casparvl commented Jan 24, 2024

eessi-bot bot commented Jan 24, 2024 • edited Loading

eessi-bot bot commented Jan 24, 2024 • edited Loading

eessi-bot bot commented Jan 24, 2024 • edited Loading

eessi-bot bot commented Jan 24, 2024 • edited Loading

eessi-bot bot commented Jan 24, 2024 • edited Loading

eessi-bot bot commented Jan 24, 2024 • edited Loading

eessi-bot bot commented Jan 24, 2024 • edited Loading

eessi-bot bot commented Jan 24, 2024 • edited Loading

casparvl commented Jan 24, 2024

APN-Pucky commented Jan 24, 2024

eessi-bot bot commented Jan 24, 2024

casparvl commented Jan 24, 2024

casparvl left a comment

Choose a reason for hiding this comment

eessi-bot bot commented Jan 22, 2024 •

edited

Loading

eessi-bot bot commented Jan 22, 2024 •

edited

Loading

casparvl commented Jan 22, 2024 •

edited

Loading

eessi-bot bot commented Jan 24, 2024 •

edited

Loading

eessi-bot bot commented Jan 24, 2024 •

edited

Loading

eessi-bot bot commented Jan 24, 2024 •

edited

Loading

eessi-bot bot commented Jan 24, 2024 •

edited

Loading

eessi-bot bot commented Jan 24, 2024 •

edited

Loading

eessi-bot bot commented Jan 24, 2024 •

edited

Loading

eessi-bot bot commented Jan 24, 2024 •

edited

Loading

eessi-bot bot commented Jan 24, 2024 •

edited

Loading

eessi-bot bot commented Jan 24, 2024 •

edited

Loading

eessi-bot bot commented Jan 24, 2024 •

edited

Loading