software-layer
software-layer copied to clipboard
{2023.6}[2023b,a64fx] ESPResSo 4.2.2 + pyMBE 0.8.0
I'm using this PR to verify that the changes made for support builds for dev.eessi.io don't cause trouble for the software.eessi.io builds, so it sits on top of:
- #771
This PR shouldn't be merged until #771 is merged, so marking it as draft...
Instance eessi-bot-mc-aws is configured to build for:
- architectures:
x86_64/generic,x86_64/intel/haswell,x86_64/intel/skylake_avx512,x86_64/amd/zen2,x86_64/amd/zen3,aarch64/generic,aarch64/neoverse_n1,aarch64/neoverse_v1 - repositories:
eessi.io-2023.06-compat,eessi-hpc.org-2023.06-software,eessi-hpc.org-2023.06-compat,eessi.io-2023.06-software
Instance eessi-bot-mc-azure is configured to build for:
- architectures:
x86_64/amd/zen4 - repositories:
eessi-hpc.org-2023.06-software,eessi-hpc.org-2023.06-compat,eessi.io-2023.06-software,eessi.io-2023.06-compat
bot: build repo:eessi.io-2023.06-software arch:aarch64/a64fx
Updates by the bot instance eessi-bot-mc-aws
(click for details)
-
received bot command
build repo:eessi.io-2023.06-software arch:aarch64/a64fxfromboegel- expanded format:
build repository:eessi.io-2023.06-software architecture:aarch64/a64fx
- expanded format:
-
handling command
build repository:eessi.io-2023.06-software architecture:aarch64/a64fxresulted in:- no jobs were submitted
Updates by the bot instance boegel-bot-deucalion
(click for details)
-
received bot command
build repo:eessi.io-2023.06-software arch:aarch64/a64fxfromboegel- expanded format:
build repository:eessi.io-2023.06-software architecture:aarch64/a64fx
- expanded format:
-
handling command
build repository:eessi.io-2023.06-software architecture:aarch64/a64fxresulted in:- submitted job
161293, for details & status see https://github.com/EESSI/software-layer/pull/782#issuecomment-2407703259
- submitted job
Updates by the bot instance eessi-bot-mc-azure
(click for details)
-
received bot command
build repo:eessi.io-2023.06-software arch:aarch64/a64fxfromboegel- expanded format:
build repository:eessi.io-2023.06-software architecture:aarch64/a64fx
- expanded format:
-
handling command
build repository:eessi.io-2023.06-software architecture:aarch64/a64fxresulted in:- no jobs were submitted
New job on instance boegel-bot-deucalion for CPU micro-architecture aarch64-a64fx for repository eessi.io-2023.06-software in job dir /home/kehoste/project_dir/bot/jobs/2024.10/pr_782/161293
| date | job status | comment |
|---|---|---|
| Oct 11 15:58:47 UTC 2024 | submitted | job id 161293 awaits release by job manager |
| Oct 11 15:59:33 UTC 2024 | released | job awaits launch by Slurm scheduler |
| Oct 11 16:00:36 UTC 2024 | running | job 161293 is running |
| Oct 11 22:29:49 UTC 2024 | finished | :grin: SUCCESS (click triangle for details)
|
| Oct 11 22:29:49 UTC 2024 | test result | :cry: FAILURE (click triangle for details)
|
| Oct 12 20:16:06 UTC 2024 | uploaded | transfer of eessi-2023.06-software-linux-aarch64-a64fx-1728684016.tar.gz to S3 bucket succeeded |
@bedroge The 2023.06/init/minimal_eessi_env that's being deployed in here is due to the changes to it in #771, we should've done a build & deploy in there...
This was deployed and ingested, but it turned out that this somehow included a wrong/old and broken version of minimal_eessi_env, so I've rolled back the transaction. We should do a rebuild here to make sure that the latest version is included, or do this in a separate PR.
This was deployed and ingested, but it turned out that this somehow included a wrong/old and broken version of
minimal_eessi_env, so I've rolled back the transaction. We should do a rebuild here to make sure that the latest version is included, or do this in a separate PR.
The build was done before the commit that adds a guard for $EESSI_COMPAT_LAYER_DIR being defined was added, see https://github.com/EESSI/software-layer/commit/1afc5995b7f53a11f8f196d1f0a7c764c348b755
Easiest way forward is just doing the build again here, which should pick up on the correct init/minimal_eessi_env...
bot: build repo:eessi.io-2023.06-software arch:aarch64/a64fx
Updates by the bot instance eessi-bot-mc-aws
(click for details)
-
received bot command
build repo:eessi.io-2023.06-software arch:aarch64/a64fxfromboegel- expanded format:
build repository:eessi.io-2023.06-software architecture:aarch64/a64fx
- expanded format:
-
handling command
build repository:eessi.io-2023.06-software architecture:aarch64/a64fxresulted in:- no jobs were submitted
Updates by the bot instance eessi-bot-mc-azure
(click for details)
-
received bot command
build repo:eessi.io-2023.06-software arch:aarch64/a64fxfromboegel- expanded format:
build repository:eessi.io-2023.06-software architecture:aarch64/a64fx
- expanded format:
-
handling command
build repository:eessi.io-2023.06-software architecture:aarch64/a64fxresulted in:- no jobs were submitted
Updates by the bot instance boegel-bot-deucalion
(click for details)
-
received bot command
build repo:eessi.io-2023.06-software arch:aarch64/a64fxfromboegel- expanded format:
build repository:eessi.io-2023.06-software architecture:aarch64/a64fx
- expanded format:
-
handling command
build repository:eessi.io-2023.06-software architecture:aarch64/a64fxresulted in:- submitted job
167582, for details & status see https://github.com/EESSI/software-layer/pull/782#issuecomment-2410540162
- submitted job
New job on instance boegel-bot-deucalion for CPU micro-architecture aarch64-a64fx for repository eessi.io-2023.06-software in job dir /home/kehoste/project_dir/bot/jobs/2024.10/pr_782/167582
| date | job status | comment |
|---|---|---|
| Oct 14 09:13:22 UTC 2024 | submitted | job id 167582 awaits release by job manager |
| Oct 14 09:14:05 UTC 2024 | released | job awaits launch by Slurm scheduler |
| Oct 14 09:15:09 UTC 2024 | running | job 167582 is running |
| Oct 14 15:34:54 UTC 2024 | finished | :grin: SUCCESS (click triangle for details)
|
| Oct 14 15:34:54 UTC 2024 | test result | :cry: FAILURE (click triangle for details)
|
| Oct 14 15:49:02 UTC 2024 | uploaded | transfer of eessi-2023.06-software-linux-aarch64-a64fx-1728918317.tar.gz to S3 bucket succeeded |
@bedroge Can you verify that the init/minimal_eessi_env in the tarball is correct now?
@bedroge Can you verify that the
init/minimal_eessi_envin the tarball is correct now?
Extracted the tarball and did a diff with the file from the software-layer repo:
[bob@multixscale-stratum0 tmp]$ diff 2023.06/init/minimal_eessi_env software-layer/init/minimal_eessi_env
[bob@multixscale-stratum0 tmp]$
And, indeed, the file now has:
# set $EPREFIX since that is basically a standard in Gentoo Prefix
# if $EESSI_COMPAT_LAYER_DIR is defined (for example by run_in_compat_layer_env.sh script), we use that value
if [ ! -z ${EESSI_COMPAT_LAYER_DIR} ]; then
export EPREFIX=$EESSI_COMPAT_LAYER_DIR
else
export EPREFIX=$EESSI_PREFIX/compat/$EESSI_OS_TYPE/$EESSI_CPU_FAMILY
fi
So, looks good to me now.
PR merged! Moved [] to /project/def-users/SHARED/trash_bin/EESSI/software-layer/2024.10.14
PR merged! Moved [] to /project/def-users/SHARED/trash_bin/EESSI/software-layer/2024.10.14