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
{{ message }}
Repository navigation
Remove existing installation directories when doing rebuilds - #339
Builds in EESSI/software-layer#1862 are failing, because tests are apparently picking up binaries from the original installation, which is not wiped yet. Let's see if this will solve it.
Note: if it does, this needs some additional checks, and it should only be done in certain cases. Just kept it simple for now to be able to test it.
The hook always runs, but I've added some safeguards: it only removes the existing dir if --rebuild used, the dir already exists and is non-empty, and it requires you to set $EESSI_FORCE_EARLY_REMOVAL_OF_INSTALL_DIR=1. I've done the latter in EESSI-install-software.sh, but only for rebuilds, and only if the installpath starts with /cvmfs (to make sure that e.g. site builds on top of CVMFS also use this).
New job on instance eessi-bot-deucalion for repository eessi.io-2023.06-software
Building on: a64fx
Building for: aarch64/a64fx
Job dir: /home/eessibot/new-bot/jobs/2026.11/pr_339/2182719
date
job status
comment
Nov 03 22:20:04 UTC 2026
submitted
job id 2182719 awaits release by job manager
Nov 03 22:20:22 UTC 2026
released
job awaits launch by Slurm scheduler
Nov 03 22:21:28 UTC 2026
running
job 2182719 is running
Nov 03 22:32:09 UTC 2026
finished
😁 SUCCESS (click triangle for details)
Details
✅ job output file slurm-2182719.out ✅ no message matching FATAL: ✅ 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.* created!
Artefacts
eessi-2023.06-software-linux-aarch64-a64fx-17937447160.tar.zstsize: 0 MiB (37877 bytes) entries: 1 modules under 2023.06/software/linux/aarch64/a64fx/modules/all
no module files in tarball
software under 2023.06/software/linux/aarch64/a64fx/software
no software packages in tarball
reprod directories under 2023.06/software/linux/aarch64/a64fx/reprod
no reprod directories in tarball
other under 2023.06/software/linux/aarch64/a64fx
no other files in tarball
Nov 03 22:32:09 UTC 2026
test result
😁 SUCCESS (click triangle for details)
ReFrame Summary
[ SKIP ] ( 1/10) Skipping test: nodes in this partition only have 30720 MiB memory available (per node) according to the current ReFrame configuration, but 49152 MiB is needed [ SKIP ] ( 2/10) Skipping test: nodes in this partition only have 30720 MiB memory available (per node) according to the current ReFrame configuration, but 49152 MiB is needed [ SKIP ] ( 3/10) Skipping test: nodes in this partition only have 30720 MiB memory available (per node) according to the current ReFrame configuration, but 49152 MiB is needed [ SKIP ] ( 4/10) Skipping test: nodes in this partition only have 30720 MiB memory available (per node) according to the current ReFrame configuration, but 49152 MiB is needed [ OK ] ( 5/10) EESSI_LAMMPS_lj %device_type=cpu %module_info=('BotBuildTests:a64fx', 'default', 'LAMMPS/2Aug2023_update2-foss-2023a-kokkos') %scale=1_node /a7d4ddbc @BotBuildTests:a64fx+default P: perf: 579.736 timesteps/s (r:0, l:None, u:None) [ OK ] ( 6/10) EESSI_LAMMPS_lj %device_type=cpu %module_info=('BotBuildTests:a64fx', 'default', 'LAMMPS/29Aug2024-foss-2023b-kokkos') %scale=1_node /60400152 @BotBuildTests:a64fx+default P: perf: 578.958 timesteps/s (r:0, l:None, u:None) [ OK ] ( 7/10) EESSI_OSU_pt2pt_CPU %benchmark_info=mpi.pt2pt.osu_latency %module_info=('BotBuildTests:a64fx', 'default', 'OSU-Micro-Benchmarks/7.2-gompi-2023b') %scale=1_node /e1b5de1d @BotBuildTests:a64fx+default P: latency: 1.21 us (r:0, l:None, u:None) [ OK ] ( 8/10) EESSI_OSU_pt2pt_CPU %benchmark_info=mpi.pt2pt.osu_latency %module_info=('BotBuildTests:a64fx', 'default', 'OSU-Micro-Benchmarks/7.1-1-gompi-2023a') %scale=1_node /8b341075 @BotBuildTests:a64fx+default P: latency: 1.22 us (r:0, l:None, u:None) [ OK ] ( 9/10) EESSI_OSU_pt2pt_CPU %benchmark_info=mpi.pt2pt.osu_bw %module_info=('BotBuildTests:a64fx', 'default', 'OSU-Micro-Benchmarks/7.2-gompi-2023b') %scale=1_node /5d554c48 @BotBuildTests:a64fx+default P: bandwidth: 8725.05 MB/s (r:0, l:None, u:None) [ OK ] (10/10) EESSI_OSU_pt2pt_CPU %benchmark_info=mpi.pt2pt.osu_bw %module_info=('BotBuildTests:a64fx', 'default', 'OSU-Micro-Benchmarks/7.1-1-gompi-2023a') %scale=1_node /0d7a6936 @BotBuildTests:a64fx+default P: bandwidth: 8728.32 MB/s (r:0, l:None, u:None) [ PASSED ] Ran 6/10 test case(s) from 10 check(s) (0 failure(s), 4 skipped, 0 aborted)
Details
✅ job output file slurm-2182719.out ✅ no message matching ERROR: ✅ no message matching [\s*FAILED\s*].*Ran .* test case
Nov 04 08:19:18 UTC 2026
uploaded
transfer of eessi-2023.06-software-linux-aarch64-a64fx-17937447160.tar.zst to S3 bucket succeeded
New job on instance eessi-bot-deucalion for repository eessi.io-2025.06-software
Building on: a64fx
Building for: aarch64/a64fx
Job dir: /home/eessibot/new-bot/jobs/2026.11/pr_339/2182720
date
job status
comment
Nov 03 22:20:10 UTC 2026
submitted
job id 2182720 awaits release by job manager
Nov 03 22:20:19 UTC 2026
released
job awaits launch by Slurm scheduler
Nov 03 22:21:31 UTC 2026
running
job 2182720 is running
Nov 03 22:27:59 UTC 2026
finished
😁 SUCCESS (click triangle for details)
Details
✅ job output file slurm-2182720.out ✅ no message matching FATAL: ✅ 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.* created!
Artefacts
eessi-2025.06-software-linux-aarch64-a64fx-17937445860.tar.zstsize: 0 MiB (37886 bytes) entries: 1 modules under 2025.06/software/linux/aarch64/a64fx/modules/all
no module files in tarball
software under 2025.06/software/linux/aarch64/a64fx/software
no software packages in tarball
reprod directories under 2025.06/software/linux/aarch64/a64fx/reprod
no reprod directories in tarball
other under 2025.06/software/linux/aarch64/a64fx
no other files in tarball
Nov 03 22:27:59 UTC 2026
test result
😢 FAILURE (click triangle for details)
Reason
EESSI test suite produced failures.
ReFrame Summary
[ FAILED ] Ran 6/6 test case(s) from 6 check(s) (6 failure(s), 0 skipped, 0 aborted)
Details
✅ job output file slurm-2182720.out ❌ found message matching ERROR: ❌ found message matching [\s*FAILED\s*].*Ran .* test case
Nov 04 08:19:37 UTC 2026
uploaded
transfer of eessi-2025.06-software-linux-aarch64-a64fx-17937445860.tar.zst to S3 bucket succeeded
New job on instance eessi-bot-deucalion for repository eessi.io-2026.06-software
Building on: a64fx
Building for: aarch64/a64fx
Job dir: /home/eessibot/new-bot/jobs/2026.11/pr_339/2182721
date
job status
comment
Nov 03 22:20:16 UTC 2026
submitted
job id 2182721 awaits release by job manager
Nov 03 22:21:25 UTC 2026
released
job awaits launch by Slurm scheduler
Nov 03 22:22:35 UTC 2026
running
job 2182721 is running
Nov 03 22:25:53 UTC 2026
finished
😁 SUCCESS (click triangle for details)
Details
✅ job output file slurm-2182721.out ✅ no message matching FATAL: ✅ 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.* created!
Artefacts
eessi-2026.06-software-linux-aarch64-a64fx-17937445870.tar.zstsize: 0 MiB (37831 bytes) entries: 1 modules under 2026.06/software/linux/aarch64/a64fx/modules/all
no module files in tarball
software under 2026.06/software/linux/aarch64/a64fx/software
no software packages in tarball
reprod directories under 2026.06/software/linux/aarch64/a64fx/reprod
no reprod directories in tarball
other under 2026.06/software/linux/aarch64/a64fx
no other files in tarball
Nov 03 22:25:53 UTC 2026
test result
😢 FAILURE (click triangle for details)
Reason
EESSI test suite produced failures.
ReFrame Summary
[ FAILED ] Ran 4/4 test case(s) from 4 check(s) (4 failure(s), 0 expected failure(s), 0 skipped, 0 aborted)
Details
✅ job output file slurm-2182721.out ❌ found message matching ERROR: ❌ found message matching [\s*FAILED\s*].*Ran .* test case
Nov 04 08:19:29 UTC 2026
uploaded
transfer of eessi-2026.06-software-linux-aarch64-a64fx-17937445870.tar.zst to S3 bucket succeeded
This file contains hidden or 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
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.
Builds in EESSI/software-layer#1862 are failing, because tests are apparently picking up binaries from the original installation, which is not wiped yet. Let's see if this will solve it.
Note: if it does, this needs some additional checks, and it should only be done in certain cases. Just kept it simple for now to be able to test it.The hook always runs, but I've added some safeguards: it only removes the existing dir if
--rebuildused, the dir already exists and is non-empty, and it requires you to set$EESSI_FORCE_EARLY_REMOVAL_OF_INSTALL_DIR=1. I've done the latter inEESSI-install-software.sh, but only for rebuilds, and only if the installpath starts with/cvmfs(to make sure that e.g. site builds on top of CVMFS also use this).