Skip to content

Conversation

agimenog
Copy link
Contributor

@agimenog agimenog commented Sep 4, 2025

Based on #1005 and #1008

@agimenog
Copy link
Contributor Author

agimenog commented Sep 4, 2025

bot: build repo:eessi.io-2023.06-software instance:eessi-bot-deucalion for:arch=aarch64/a64fx

@eessi-bot-deucalion
Copy link

eessi-bot-deucalion bot commented Sep 4, 2025

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/2025.09/pr_1177/534565

date job status comment
Sep 04 15:51:27 UTC 2025 submitted job id 534565 awaits release by job manager
Sep 04 15:52:05 UTC 2025 released job awaits launch by Slurm scheduler
Sep 04 15:53:10 UTC 2025 running job 534565 is running
Sep 04 16:02:48 UTC 2025 finished
😢 FAILURE (click triangle for details)
Details
✅ job output file slurm-534565.out
✅ no message matching FATAL:
❌ found message matching ERROR:
✅ no message matching FAILED:
❌ found message matching required modules missing:
❌ no message matching No missing installations
✅ found message matching .tar.gz created!
Artefacts
eessi-2023.06-software-linux-aarch64-a64fx-17570014330.tar.gzsize: 0 MiB (45 bytes)
entries: 0
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
Sep 04 16:02:48 UTC 2025 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) accodring 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) accodring 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) accodring 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) accodring to the current ReFrame configuration, but 49152 MiB is needed
[ OK ] ( 5/10) EESSI_LAMMPS_lj %device_type=cpu %module_name=LAMMPS/29Aug2024-foss-2023b-kokkos %scale=1_node /aeb2d9df @BotBuildTests:aarch64_a64fx+default
P: perf: 582.517 timesteps/s (r:0, l:None, u:None)
[ OK ] ( 6/10) EESSI_LAMMPS_lj %device_type=cpu %module_name=LAMMPS/2Aug2023_update2-foss-2023a-kokkos %scale=1_node /04ff9ece @BotBuildTests:aarch64_a64fx+default
P: perf: 583.396 timesteps/s (r:0, l:None, u:None)
[ OK ] ( 7/10) EESSI_OSU_pt2pt_CPU %benchmark_info=mpi.pt2pt.osu_latency %module_name=OSU-Micro-Benchmarks/7.2-gompi-2023b %scale=1_node /15cad6c4 @BotBuildTests:aarch64_a64fx+default
P: latency: 1.66 us (r:0, l:None, u:None)
[ OK ] ( 8/10) EESSI_OSU_pt2pt_CPU %benchmark_info=mpi.pt2pt.osu_latency %module_name=OSU-Micro-Benchmarks/7.1-1-gompi-2023a %scale=1_node /6672deda @BotBuildTests:aarch64_a64fx+default
P: latency: 1.72 us (r:0, l:None, u:None)
[ OK ] ( 9/10) EESSI_OSU_pt2pt_CPU %benchmark_info=mpi.pt2pt.osu_bw %module_name=OSU-Micro-Benchmarks/7.2-gompi-2023b %scale=1_node /2a9a47b1 @BotBuildTests:aarch64_a64fx+default
P: bandwidth: 8289.6 MB/s (r:0, l:None, u:None)
[ OK ] (10/10) EESSI_OSU_pt2pt_CPU %benchmark_info=mpi.pt2pt.osu_bw %module_name=OSU-Micro-Benchmarks/7.1-1-gompi-2023a %scale=1_node /1b24ab8e @BotBuildTests:aarch64_a64fx+default
P: bandwidth: 8711.51 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-534565.out
❌ found message matching ERROR:
✅ no message matching [\s*FAILED\s*].*Ran .* test case

@boegel
Copy link
Contributor

boegel commented Sep 8, 2025

@agimenog Last build didn't work out as hoped?

@agimenog
Copy link
Contributor Author

agimenog commented Sep 8, 2025

@boegel It seems so, I will check the logs to see where the problem is

@agimenog
Copy link
Contributor Author

bot: build repo:eessi.io-2023.06-software instance:eessi-bot-deucalion for:arch=aarch64/a64fx

@eessi-bot-deucalion
Copy link

eessi-bot-deucalion bot commented Sep 18, 2025

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/2025.09/pr_1177/549821

date job status comment
Sep 18 12:30:57 UTC 2025 submitted job id 549821 awaits release by job manager
Sep 18 12:32:02 UTC 2025 released job awaits launch by Slurm scheduler
Sep 18 12:33:04 UTC 2025 running job 549821 is running
Sep 18 13:37:49 UTC 2025 finished
😢 FAILURE (click triangle for details)
Details
✅ job output file slurm-549821.out
✅ no message matching FATAL:
❌ 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
eessi-2023.06-software-linux-aarch64-a64fx-17582023010.tar.gzsize: 37 MiB (39395735 bytes)
entries: 5986
modules under 2023.06/software/linux/aarch64/a64fx/modules/all
Ninja/1.11.1-GCCcore-12.2.0.lua
PCRE2/10.40-GCCcore-12.2.0.lua
Python/2.7.18-GCCcore-12.2.0-bare.lua
double-conversion/3.2.1-GCCcore-12.2.0.lua
libpng/1.6.38-GCCcore-12.2.0.lua
re2c/3.0-GCCcore-12.2.0.lua
software under 2023.06/software/linux/aarch64/a64fx/software
Ninja/1.11.1-GCCcore-12.2.0
PCRE2/10.40-GCCcore-12.2.0
Python/2.7.18-GCCcore-12.2.0-bare
double-conversion/3.2.1-GCCcore-12.2.0
libpng/1.6.38-GCCcore-12.2.0
re2c/3.0-GCCcore-12.2.0
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
Sep 18 13:37:49 UTC 2025 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) accodring 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) accodring 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) accodring 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) accodring to the current ReFrame configuration, but 49152 MiB is needed
[ OK ] ( 5/10) EESSI_LAMMPS_lj %device_type=cpu %module_name=LAMMPS/29Aug2024-foss-2023b-kokkos %scale=1_node /aeb2d9df @BotBuildTests:aarch64_a64fx+default
P: perf: 581.914 timesteps/s (r:0, l:None, u:None)
[ OK ] ( 6/10) EESSI_LAMMPS_lj %device_type=cpu %module_name=LAMMPS/2Aug2023_update2-foss-2023a-kokkos %scale=1_node /04ff9ece @BotBuildTests:aarch64_a64fx+default
P: perf: 580.69 timesteps/s (r:0, l:None, u:None)
[ OK ] ( 7/10) EESSI_OSU_pt2pt_CPU %benchmark_info=mpi.pt2pt.osu_latency %module_name=OSU-Micro-Benchmarks/7.2-gompi-2023b %scale=1_node /15cad6c4 @BotBuildTests:aarch64_a64fx+default
P: latency: 1.65 us (r:0, l:None, u:None)
[ OK ] ( 8/10) EESSI_OSU_pt2pt_CPU %benchmark_info=mpi.pt2pt.osu_latency %module_name=OSU-Micro-Benchmarks/7.1-1-gompi-2023a %scale=1_node /6672deda @BotBuildTests:aarch64_a64fx+default
P: latency: 1.68 us (r:0, l:None, u:None)
[ OK ] ( 9/10) EESSI_OSU_pt2pt_CPU %benchmark_info=mpi.pt2pt.osu_bw %module_name=OSU-Micro-Benchmarks/7.2-gompi-2023b %scale=1_node /2a9a47b1 @BotBuildTests:aarch64_a64fx+default
P: bandwidth: 8766.86 MB/s (r:0, l:None, u:None)
[ OK ] (10/10) EESSI_OSU_pt2pt_CPU %benchmark_info=mpi.pt2pt.osu_bw %module_name=OSU-Micro-Benchmarks/7.1-1-gompi-2023a %scale=1_node /1b24ab8e @BotBuildTests:aarch64_a64fx+default
P: bandwidth: 8660.47 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-549821.out
❌ found message matching ERROR:
✅ no message matching [\s*FAILED\s*].*Ran .* test case

@bedroge
Copy link
Collaborator

bedroge commented Sep 23, 2025

These builds didn't work because of the Rust 1.65.0 issue. The updated hook from EESSI/software-layer-scripts#86 should make sure that we use Rust 1.75.0 (from #1200), so let's give this another try.

bot: build repo:eessi.io-2023.06-software instance:eessi-bot-deucalion for:arch=aarch64/a64fx

@eessi-bot-deucalion
Copy link

eessi-bot-deucalion bot commented Sep 23, 2025

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/2025.09/pr_1177/553732

date job status comment
Sep 23 20:16:55 UTC 2025 submitted job id 553732 awaits release by job manager
Sep 23 20:16:59 UTC 2025 released job awaits launch by Slurm scheduler
Sep 23 20:18:02 UTC 2025 running job 553732 is running
Sep 23 20:26:19 UTC 2025 finished
😢 FAILURE (click triangle for details)
Details
✅ job output file slurm-553732.out
✅ no message matching FATAL:
❌ found message matching ERROR:
✅ no message matching FAILED:
✅ no message matching required modules missing:
❌ no message matching No missing installations
✅ found message matching .tar.gz created!
Artefacts
eessi-2023.06-software-linux-aarch64-a64fx-17586588100.tar.gzsize: 0 MiB (45 bytes)
entries: 0
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
Sep 23 20:26:19 UTC 2025 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) accodring 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) accodring 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) accodring 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) accodring to the current ReFrame configuration, but 49152 MiB is needed
[ OK ] ( 5/10) EESSI_LAMMPS_lj %device_type=cpu %module_name=LAMMPS/29Aug2024-foss-2023b-kokkos %scale=1_node /aeb2d9df @BotBuildTests:aarch64_a64fx+default
P: perf: 582.68 timesteps/s (r:0, l:None, u:None)
[ OK ] ( 6/10) EESSI_LAMMPS_lj %device_type=cpu %module_name=LAMMPS/2Aug2023_update2-foss-2023a-kokkos %scale=1_node /04ff9ece @BotBuildTests:aarch64_a64fx+default
P: perf: 585.195 timesteps/s (r:0, l:None, u:None)
[ OK ] ( 7/10) EESSI_OSU_pt2pt_CPU %benchmark_info=mpi.pt2pt.osu_latency %module_name=OSU-Micro-Benchmarks/7.2-gompi-2023b %scale=1_node /15cad6c4 @BotBuildTests:aarch64_a64fx+default
P: latency: 1.68 us (r:0, l:None, u:None)
[ OK ] ( 8/10) EESSI_OSU_pt2pt_CPU %benchmark_info=mpi.pt2pt.osu_latency %module_name=OSU-Micro-Benchmarks/7.1-1-gompi-2023a %scale=1_node /6672deda @BotBuildTests:aarch64_a64fx+default
P: latency: 1.69 us (r:0, l:None, u:None)
[ OK ] ( 9/10) EESSI_OSU_pt2pt_CPU %benchmark_info=mpi.pt2pt.osu_bw %module_name=OSU-Micro-Benchmarks/7.2-gompi-2023b %scale=1_node /2a9a47b1 @BotBuildTests:aarch64_a64fx+default
P: bandwidth: 8767.94 MB/s (r:0, l:None, u:None)
[ OK ] (10/10) EESSI_OSU_pt2pt_CPU %benchmark_info=mpi.pt2pt.osu_bw %module_name=OSU-Micro-Benchmarks/7.1-1-gompi-2023a %scale=1_node /1b24ab8e @BotBuildTests:aarch64_a64fx+default
P: bandwidth: 8686.3 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-553732.out
❌ found message matching ERROR:
✅ no message matching [\s*FAILED\s*].*Ran .* test case

@bedroge
Copy link
Collaborator

bedroge commented Sep 24, 2025

bot: build repo:eessi.io-2023.06-software instance:eessi-bot-deucalion for:arch=aarch64/a64fx

@eessi-bot-deucalion
Copy link

eessi-bot-deucalion bot commented Sep 24, 2025

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/2025.09/pr_1177/553802

date job status comment
Sep 24 05:20:04 UTC 2025 submitted job id 553802 awaits release by job manager
Sep 24 05:20:43 UTC 2025 released job awaits launch by Slurm scheduler
Sep 24 05:21:46 UTC 2025 running job 553802 is running
Sep 24 05:58:12 UTC 2025 finished
😢 FAILURE (click triangle for details)
Details
✅ job output file slurm-553802.out
✅ no message matching FATAL:
❌ 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
eessi-2023.06-software-linux-aarch64-a64fx-17586932340.tar.gzsize: 35 MiB (37067751 bytes)
entries: 6044
modules under 2023.06/software/linux/aarch64/a64fx/modules/all
Mako/1.2.4-GCCcore-12.2.0.lua
NASM/2.15.05-GCCcore-12.2.0.lua
NSPR/4.35-GCCcore-12.2.0.lua
Python/2.7.18-GCCcore-12.2.0-bare.lua
double-conversion/3.2.1-GCCcore-12.2.0.lua
graphite2/1.3.14-GCCcore-12.2.0.lua
libjpeg-turbo/2.1.4-GCCcore-12.2.0.lua
re2c/3.0-GCCcore-12.2.0.lua
snappy/1.1.9-GCCcore-12.2.0.lua
software under 2023.06/software/linux/aarch64/a64fx/software
Mako/1.2.4-GCCcore-12.2.0
NASM/2.15.05-GCCcore-12.2.0
NSPR/4.35-GCCcore-12.2.0
Python/2.7.18-GCCcore-12.2.0-bare
double-conversion/3.2.1-GCCcore-12.2.0
graphite2/1.3.14-GCCcore-12.2.0
libjpeg-turbo/2.1.4-GCCcore-12.2.0
re2c/3.0-GCCcore-12.2.0
snappy/1.1.9-GCCcore-12.2.0
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
Sep 24 05:58:12 UTC 2025 test result
😢 FAILURE (click triangle for details)
Reason
EESSI test suite was not run, test step itself failed to execute.
Details
✅ job output file slurm-553802.out
❌ found message matching ERROR:
✅ no message matching [\s*FAILED\s*].*Ran .* test case

@bedroge
Copy link
Collaborator

bedroge commented Sep 24, 2025

Still failed because of the same issue with terse, maybe I was a bit too early. Let's try again.

bot: build repo:eessi.io-2023.06-software instance:eessi-bot-deucalion for:arch=aarch64/a64fx

edit: ah, no, I checked the wrong log file. The last build actually failed because of a download issue:

== Running pre-fetch hook...
  >> download failed: https://ftp.mozilla.org/pub/security/nss/releases/NSS_3_85_RTM/src/nss-3.85.tar.gz
  >> download failed: https://sources.easybuild.io/n/NSS/nss-3.85.tar.gz
== ... (took 51 secs)
== FAILED: Installation ended unsuccessfully (build directory: /tmp/eessibot/easybuild/build/NSS/3.85/GCCcore-12.2.0): build failed (first 300 chars): Couldn't find file nss-3.85.tar.g
z anywhere, and downloading it didn't work either... Paths attempted (in order): /cvmfs/software.eessi.io/versions/2023.06/software/linux/aarch64/a64fx/software/EasyBuild/4.8.2/easybui
ld/easyconfigs/n/NSS/n/NSS/nss-3.85.tar.gz, /cvmfs/software.eessi.io/versions/2023. (took 51 secs)

I can download that file without any issues, so let's see what happens this time.

@eessi-bot-deucalion
Copy link

eessi-bot-deucalion bot commented Sep 24, 2025

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/2025.09/pr_1177/553817

date job status comment
Sep 24 07:09:48 UTC 2025 submitted job id 553817 awaits release by job manager
Sep 24 07:10:31 UTC 2025 released job awaits launch by Slurm scheduler
Sep 24 07:11:35 UTC 2025 running job 553817 is running
Sep 24 10:55:06 UTC 2025 finished
😢 FAILURE (click triangle for details)
Details
✅ job output file slurm-553817.out
✅ no message matching FATAL:
❌ 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
eessi-2023.06-software-linux-aarch64-a64fx-17587108930.tar.gzsize: 79 MiB (83552917 bytes)
entries: 9174
modules under 2023.06/software/linux/aarch64/a64fx/modules/all
JasPer/4.0.0-GCCcore-12.2.0.lua
Mako/1.2.4-GCCcore-12.2.0.lua
NASM/2.15.05-GCCcore-12.2.0.lua
NSPR/4.35-GCCcore-12.2.0.lua
NSS/3.85-GCCcore-12.2.0.lua
Python/2.7.18-GCCcore-12.2.0-bare.lua
double-conversion/3.2.1-GCCcore-12.2.0.lua
graphite2/1.3.14-GCCcore-12.2.0.lua
gzip/1.12-GCCcore-12.2.0.lua
libdrm/2.4.114-GCCcore-12.2.0.lua
libglvnd/1.6.0-GCCcore-12.2.0.lua
libjpeg-turbo/2.1.4-GCCcore-12.2.0.lua
libunwind/1.6.2-GCCcore-12.2.0.lua
lz4/1.9.4-GCCcore-12.2.0.lua
nodejs/18.12.1-GCCcore-12.2.0.lua
re2c/3.0-GCCcore-12.2.0.lua
snappy/1.1.9-GCCcore-12.2.0.lua
zstd/1.5.2-GCCcore-12.2.0.lua
software under 2023.06/software/linux/aarch64/a64fx/software
JasPer/4.0.0-GCCcore-12.2.0
Mako/1.2.4-GCCcore-12.2.0
NASM/2.15.05-GCCcore-12.2.0
NSPR/4.35-GCCcore-12.2.0
NSS/3.85-GCCcore-12.2.0
Python/2.7.18-GCCcore-12.2.0-bare
double-conversion/3.2.1-GCCcore-12.2.0
graphite2/1.3.14-GCCcore-12.2.0
gzip/1.12-GCCcore-12.2.0
libdrm/2.4.114-GCCcore-12.2.0
libglvnd/1.6.0-GCCcore-12.2.0
libjpeg-turbo/2.1.4-GCCcore-12.2.0
libunwind/1.6.2-GCCcore-12.2.0
lz4/1.9.4-GCCcore-12.2.0
nodejs/18.12.1-GCCcore-12.2.0
re2c/3.0-GCCcore-12.2.0
snappy/1.1.9-GCCcore-12.2.0
zstd/1.5.2-GCCcore-12.2.0
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
Sep 24 10:55:06 UTC 2025 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) accodring 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) accodring 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) accodring 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) accodring to the current ReFrame configuration, but 49152 MiB is needed
[ OK ] ( 5/10) EESSI_LAMMPS_lj %device_type=cpu %module_name=LAMMPS/29Aug2024-foss-2023b-kokkos %scale=1_node /aeb2d9df @BotBuildTests:aarch64_a64fx+default
P: perf: 582.189 timesteps/s (r:0, l:None, u:None)
[ OK ] ( 6/10) EESSI_LAMMPS_lj %device_type=cpu %module_name=LAMMPS/2Aug2023_update2-foss-2023a-kokkos %scale=1_node /04ff9ece @BotBuildTests:aarch64_a64fx+default
P: perf: 585.048 timesteps/s (r:0, l:None, u:None)
[ OK ] ( 7/10) EESSI_OSU_pt2pt_CPU %benchmark_info=mpi.pt2pt.osu_latency %module_name=OSU-Micro-Benchmarks/7.2-gompi-2023b %scale=1_node /15cad6c4 @BotBuildTests:aarch64_a64fx+default
P: latency: 1.72 us (r:0, l:None, u:None)
[ OK ] ( 8/10) EESSI_OSU_pt2pt_CPU %benchmark_info=mpi.pt2pt.osu_latency %module_name=OSU-Micro-Benchmarks/7.1-1-gompi-2023a %scale=1_node /6672deda @BotBuildTests:aarch64_a64fx+default
P: latency: 1.7 us (r:0, l:None, u:None)
[ OK ] ( 9/10) EESSI_OSU_pt2pt_CPU %benchmark_info=mpi.pt2pt.osu_bw %module_name=OSU-Micro-Benchmarks/7.2-gompi-2023b %scale=1_node /2a9a47b1 @BotBuildTests:aarch64_a64fx+default
P: bandwidth: 8480.33 MB/s (r:0, l:None, u:None)
[ OK ] (10/10) EESSI_OSU_pt2pt_CPU %benchmark_info=mpi.pt2pt.osu_bw %module_name=OSU-Micro-Benchmarks/7.1-1-gompi-2023a %scale=1_node /1b24ab8e @BotBuildTests:aarch64_a64fx+default
P: bandwidth: 8555.65 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-553817.out
❌ found message matching ERROR:
✅ no message matching [\s*FAILED\s*].*Ran .* test case

@bedroge
Copy link
Collaborator

bedroge commented Sep 24, 2025

The LLVM build failed:

/tmp/eb-2llwp9cq/eb-fxhc1oex/cck4kRMa.s: Assembler messages:
/tmp/eb-2llwp9cq/eb-fxhc1oex/cck4kRMa.s:18047: Error: immediate offset out of range 0 to 31 at operand 3 -- `st1b z2.d,p0,[z0.d,#88]'
make[2]: *** [lib/Transforms/Utils/CMakeFiles/LLVMTransformUtils.dir/build.make:289: lib/Transforms/Utils/CMakeFiles/LLVMTransformUtils.dir/CodeLayout.cpp.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: Leaving directory '/tmp/eessibot/easybuild/build/LLVM/15.0.5/GCCcore-12.2.0/easybuild_obj'
make[1]: *** [CMakeFiles/Makefile2:10253: lib/Transforms/Utils/CMakeFiles/LLVMTransformUtils.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....

This is basically the same error as we observed for Rust 1.65.0 (see #1138). That makes sense, as that particular Rust version includes LLVM 15.

@ocaisa
Copy link
Member

ocaisa commented Sep 24, 2025

I don't think we should waste more time on this, it's not a good use of our limited resources

@ocaisa
Copy link
Member

ocaisa commented Sep 24, 2025

Do you think that bumping the LLVM version might be the solution? That is likely to appear for a few packages...

@bedroge
Copy link
Collaborator

bedroge commented Sep 24, 2025

Do you think that bumping the LLVM version might be the solution? That is likely to appear for a few packages...

That might work, I checked the local stack on Deucalion and they have these versions installed with EB:

14.0.3-GCCcore-11.3.0  16.0.6-GCCcore-12.3.0  18.1.8-GCCcore-13.3.0

So we could try to bump it to 16.0.6. The good thing is that 15.0.5 only seems to be used by Mesa:
https://github.com/search?q=repo%3Aeasybuilders%2Feasybuild-easyconfigs%20LLVM%2015.0.5&type=code

@bedroge
Copy link
Collaborator

bedroge commented Oct 1, 2025

Found another workaround (which probably would have solved the Rust issue too): I tried building LLVM 15.0.5 with optarch=march=armv8.2-a and that worked. I think this basically disables SVE; don't know how much that matters for LLVM itself, but since it's not used a lot anyway, I propose we go ahead and use this solution. I'll open a PR to add this to the hooks file.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants