You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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:
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
😁 SUCCESS (click triangle for details)
Details
✅ job output file slurm-161293.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-a64fx-1728684016.tar.gzsize: 335 MiB (352166839 bytes) entries: 37026 modules under 2023.06/software/linux/aarch64/a64fx/modules/all
@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 1afc599
Easiest way forward is just doing the build again here, which should pick up on the correct init/minimal_eessi_env...
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
😁 SUCCESS (click triangle for details)
Details
✅ job output file slurm-167582.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-a64fx-1728918317.tar.gzsize: 335 MiB (352175732 bytes) entries: 37026 modules under 2023.06/software/linux/aarch64/a64fx/modules/all
EESSI test suite was not run, test step itself failed to execute.
Details
✅ job output file slurm-167582.out ❌ found message matching ERROR: ✅ no message matching [\s*FAILED\s*].*Ran .* test case
Oct 14 15:49:02 UTC 2024
uploaded
transfer of eessi-2023.06-software-linux-aarch64-a64fx-1728918317.tar.gz to S3 bucket succeeded
boegel
added
bot:deploy
Ask bot to deploy missing software installations to EESSI
and removed
bot:deploy
Ask bot to deploy missing software installations to EESSI
labels
Oct 14, 2024
# 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
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I'm using this PR to verify that the changes made for support builds for
dev.eessi.io
don't cause trouble for thesoftware.eessi.io
builds, so it sits on top of:dev.eessi.io
repository #771This PR shouldn't be merged until #771 is merged, so marking it as draft...