Skip to content

Conversation

PetrKralCZ
Copy link
Contributor

1 out of 19 required modules missing:

* RAxML/8.2.13-gompi-2023b-avx2 (RAxML-8.2.13-gompi-2023b-avx2.eb)

@boegel
Copy link
Contributor

boegel commented Sep 18, 2025

bot: build repo:eessi.io-2023.06-software instance:eessi-bot-mc-aws for:arch=x86_64/amd/zen2
bot: build repo:eessi.io-2023.06-software instance:eessi-bot-jsc for:arch=aarch64/nvidia/grace

@eessi-bot-aws
Copy link

eessi-bot-aws bot commented Sep 18, 2025

error: easystacks/software.eessi.io/2023.06/eessi-2023.06-eb-5.1.1-2023b.yml: patch does not apply

Unable to download or merge changes between the source branch and the destination branch.
Tip: This can usually be resolved by syncing your branch and resolving any merge conflicts.

1 similar comment
@eessi-bot-jsc
Copy link

eessi-bot-jsc bot commented Sep 18, 2025

error: easystacks/software.eessi.io/2023.06/eessi-2023.06-eb-5.1.1-2023b.yml: patch does not apply

Unable to download or merge changes between the source branch and the destination branch.
Tip: This can usually be resolved by syncing your branch and resolving any merge conflicts.

@boegel
Copy link
Contributor

boegel commented Sep 18, 2025

@PetrKralCZ please fix the merge conflict

@boegel
Copy link
Contributor

boegel commented Sep 18, 2025

bot: build repo:eessi.io-2023.06-software instance:eessi-bot-mc-aws for:arch=x86_64/amd/zen2
bot: build repo:eessi.io-2023.06-software instance:eessi-bot-jsc for:arch=aarch64/nvidia/grace

@eessi-bot-aws
Copy link

eessi-bot-aws bot commented Sep 18, 2025

New job on instance eessi-bot-mc-aws for repository eessi.io-2023.06-software
Building on: amd-zen2
Building for: x86_64/amd/zen2
Job dir: /project/def-users/SHARED/jobs/2025.09/pr_1196/90779

date job status comment
Sep 18 12:55:29 UTC 2025 submitted job id 90779 awaits release by job manager
Sep 18 12:56:25 UTC 2025 released job awaits launch by Slurm scheduler
Sep 18 13:00:48 UTC 2025 running job 90779 is running
Sep 18 13:04:55 UTC 2025 finished
😁 SUCCESS (click triangle for details)
Details
✅ job output file slurm-90779.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.gz created!
Artefacts
eessi-2023.06-software-linux-x86_64-amd-zen2-17582005430.tar.gzsize: 2 MiB (2586153 bytes)
entries: 32
modules under 2023.06/software/linux/x86_64/amd/zen2/modules/all
RAxML/8.2.13-gompi-2023b-avx2.lua
software under 2023.06/software/linux/x86_64/amd/zen2/software
RAxML/8.2.13-gompi-2023b-avx2
reprod directories under 2023.06/software/linux/x86_64/amd/zen2/reprod
no reprod directories in tarball
other under 2023.06/software/linux/x86_64/amd/zen2
no other files in tarball
Sep 18 13:04:55 UTC 2025 test result
😁 SUCCESS (click triangle for details)
ReFrame Summary
[ OK ] ( 1/10) EESSI_LAMMPS_lj %device_type=cpu %module_name=LAMMPS/29Aug2024-foss-2023b-kokkos %scale=1_node /aeb2d9df @BotBuildTests:x86_64_amd_zen2+default
P: perf: 264.469 timesteps/s (r:0, l:None, u:None)
[ OK ] ( 2/10) EESSI_LAMMPS_lj %device_type=cpu %module_name=LAMMPS/2Aug2023_update2-foss-2023a-kokkos %scale=1_node /04ff9ece @BotBuildTests:x86_64_amd_zen2+default
P: perf: 446.224 timesteps/s (r:0, l:None, u:None)
[ OK ] ( 3/10) EESSI_OSU_coll %benchmark_info=mpi.collective.osu_allreduce %module_name=OSU-Micro-Benchmarks/7.2-gompi-2023b %scale=1_node %device_type=cpu /775175bf @BotBuildTests:x86_64_amd_zen2+default
P: latency: 7.32 us (r:0, l:None, u:None)
[ OK ] ( 4/10) EESSI_OSU_coll %benchmark_info=mpi.collective.osu_allreduce %module_name=OSU-Micro-Benchmarks/7.1-1-gompi-2023a %scale=1_node %device_type=cpu /52707c40 @BotBuildTests:x86_64_amd_zen2+default
P: latency: 1.89 us (r:0, l:None, u:None)
[ OK ] ( 5/10) EESSI_OSU_coll %benchmark_info=mpi.collective.osu_alltoall %module_name=OSU-Micro-Benchmarks/7.2-gompi-2023b %scale=1_node %device_type=cpu /b1aacda9 @BotBuildTests:x86_64_amd_zen2+default
P: latency: 4.02 us (r:0, l:None, u:None)
[ OK ] ( 6/10) EESSI_OSU_coll %benchmark_info=mpi.collective.osu_alltoall %module_name=OSU-Micro-Benchmarks/7.1-1-gompi-2023a %scale=1_node %device_type=cpu /c6bad193 @BotBuildTests:x86_64_amd_zen2+default
P: latency: 4.23 us (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:x86_64_amd_zen2+default
P: latency: 0.56 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:x86_64_amd_zen2+default
P: latency: 0.54 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:x86_64_amd_zen2+default
P: bandwidth: 7267.66 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:x86_64_amd_zen2+default
P: bandwidth: 7288.03 MB/s (r:0, l:None, u:None)
[ PASSED ] Ran 10/10 test case(s) from 10 check(s) (0 failure(s), 0 skipped, 0 aborted)
Details
✅ job output file slurm-90779.out
✅ no message matching ERROR:
✅ no message matching [\s*FAILED\s*].*Ran .* test case

@eessi-bot-jsc
Copy link

eessi-bot-jsc bot commented Sep 18, 2025

New job on instance eessi-bot-jsc for repository eessi.io-2023.06-software
Building on: nvidia-grace
Building for: aarch64/nvidia/grace
Job dir: /p/project1/ceasybuilders/eessibot/jobs/2025.09/pr_1196/14067599

date job status comment
Sep 18 12:55:29 UTC 2025 submitted job id 14067599 awaits release by job manager
Sep 18 12:55:54 UTC 2025 released job awaits launch by Slurm scheduler
Sep 18 13:04:14 UTC 2025 running job 14067599 is running
Sep 18 13:10:40 UTC 2025 finished
😢 FAILURE (click triangle for details)
Details
✅ job output file slurm-14067599.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-nvidia-grace-17582007430.tar.gzsize: 0 MiB (45 bytes)
entries: 0
modules under 2023.06/software/linux/aarch64/nvidia/grace/modules/all
no module files in tarball
software under 2023.06/software/linux/aarch64/nvidia/grace/software
no software packages in tarball
reprod directories under 2023.06/software/linux/aarch64/nvidia/grace/reprod
no reprod directories in tarball
other under 2023.06/software/linux/aarch64/nvidia/grace
no other files in tarball
Sep 18 13:10:40 UTC 2025 test result
😁 SUCCESS (click triangle for details)
ReFrame Summary
[ SKIP ] ( 1/26) Skipping GPU test : only 1 GPU available for this test case
[ SKIP ] ( 2/26) Skipping GPU test : only 1 GPU available for this test case
[ SKIP ] ( 3/26) Skipping GPU test : only 1 GPU available for this test case
[ SKIP ] ( 4/26) Skipping GPU test : only 1 GPU available for this test case
[ SKIP ] ( 5/26) Skipping GPU test : only 1 GPU available for this test case
[ SKIP ] ( 6/26) Skipping GPU test : only 1 GPU available for this test case
[ SKIP ] ( 7/26) Skipping GPU test : only 1 GPU available for this test case
[ SKIP ] ( 8/26) Skipping GPU test : only 1 GPU available for this test case
[ OK ] ( 9/26) EESSI_LAMMPS_lj %device_type=cpu %module_name=LAMMPS/29Aug2024-foss-2023b-kokkos %scale=1_node /aeb2d9df @BotBuildTests:aarch64_nvidia_grace+default
P: perf: 1514.171 timesteps/s (r:0, l:None, u:None)
[ OK ] (10/26) EESSI_LAMMPS_lj %device_type=cpu %module_name=LAMMPS/2Aug2023_update2-foss-2023a-kokkos %scale=1_node /04ff9ece @BotBuildTests:aarch64_nvidia_grace+default
P: perf: 1523.207 timesteps/s (r:0, l:None, u:None)
[ OK ] (11/26) EESSI_OSU_coll %benchmark_info=mpi.collective.osu_allreduce %module_name=OSU-Micro-Benchmarks/7.2-gompi-2023b %scale=1_node %device_type=cpu /775175bf @BotBuildTests:aarch64_nvidia_grace+default
P: latency: 4.81 us (r:0, l:None, u:None)
[ OK ] (12/26) EESSI_OSU_coll %benchmark_info=mpi.collective.osu_allreduce %module_name=OSU-Micro-Benchmarks/7.1-1-gompi-2023a %scale=1_node %device_type=cpu /52707c40 @BotBuildTests:aarch64_nvidia_grace+default
P: latency: 5.14 us (r:0, l:None, u:None)
[ OK ] (13/26) EESSI_OSU_coll %benchmark_info=mpi.collective.osu_allreduce %module_name=OSU-Micro-Benchmarks/7.5-gompi-2023b-CUDA-12.4.0 %scale=1_node %device_type=cpu /95ac9526 @BotBuildTests:aarch64_nvidia_grace+default
P: latency: 5.12 us (r:0, l:None, u:None)
[ OK ] (14/26) EESSI_OSU_coll %benchmark_info=mpi.collective.osu_allreduce %module_name=OSU-Micro-Benchmarks/7.2-gompi-2023a-CUDA-12.1.1 %scale=1_node %device_type=cpu /1cff5d41 @BotBuildTests:aarch64_nvidia_grace+default
P: latency: 5.22 us (r:0, l:None, u:None)
[ OK ] (15/26) EESSI_OSU_coll %benchmark_info=mpi.collective.osu_alltoall %module_name=OSU-Micro-Benchmarks/7.2-gompi-2023b %scale=1_node %device_type=cpu /b1aacda9 @BotBuildTests:aarch64_nvidia_grace+default
P: latency: 7.06 us (r:0, l:None, u:None)
[ OK ] (16/26) EESSI_OSU_coll %benchmark_info=mpi.collective.osu_alltoall %module_name=OSU-Micro-Benchmarks/7.1-1-gompi-2023a %scale=1_node %device_type=cpu /c6bad193 @BotBuildTests:aarch64_nvidia_grace+default
P: latency: 7.09 us (r:0, l:None, u:None)
[ OK ] (17/26) EESSI_OSU_coll %benchmark_info=mpi.collective.osu_alltoall %module_name=OSU-Micro-Benchmarks/7.5-gompi-2023b-CUDA-12.4.0 %scale=1_node %device_type=cpu /0edb8a95 @BotBuildTests:aarch64_nvidia_grace+default
P: latency: 8.72 us (r:0, l:None, u:None)
[ OK ] (18/26) EESSI_OSU_coll %benchmark_info=mpi.collective.osu_alltoall %module_name=OSU-Micro-Benchmarks/7.2-gompi-2023a-CUDA-12.1.1 %scale=1_node %device_type=cpu /b2ab2213 @BotBuildTests:aarch64_nvidia_grace+default
P: latency: 8.42 us (r:0, l:None, u:None)
[ OK ] (19/26) 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_nvidia_grace+default
P: latency: 0.51 us (r:0, l:None, u:None)
[ OK ] (20/26) 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_nvidia_grace+default
P: latency: 0.49 us (r:0, l:None, u:None)
[ OK ] (21/26) EESSI_OSU_pt2pt_CPU %benchmark_info=mpi.pt2pt.osu_latency %module_name=OSU-Micro-Benchmarks/7.5-gompi-2023b-CUDA-12.4.0 %scale=1_node /8ec94746 @BotBuildTests:aarch64_nvidia_grace+default
P: latency: 0.5 us (r:0, l:None, u:None)
[ OK ] (22/26) EESSI_OSU_pt2pt_CPU %benchmark_info=mpi.pt2pt.osu_latency %module_name=OSU-Micro-Benchmarks/7.2-gompi-2023a-CUDA-12.1.1 %scale=1_node /1a3a497b @BotBuildTests:aarch64_nvidia_grace+default
P: latency: 0.51 us (r:0, l:None, u:None)
[ OK ] (23/26) 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_nvidia_grace+default
P: bandwidth: 42802.09 MB/s (r:0, l:None, u:None)
[ OK ] (24/26) 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_nvidia_grace+default
P: bandwidth: 40967.13 MB/s (r:0, l:None, u:None)
[ OK ] (25/26) EESSI_OSU_pt2pt_CPU %benchmark_info=mpi.pt2pt.osu_bw %module_name=OSU-Micro-Benchmarks/7.5-gompi-2023b-CUDA-12.4.0 %scale=1_node /c9ca6dc1 @BotBuildTests:aarch64_nvidia_grace+default
P: bandwidth: 41335.12 MB/s (r:0, l:None, u:None)
[ OK ] (26/26) EESSI_OSU_pt2pt_CPU %benchmark_info=mpi.pt2pt.osu_bw %module_name=OSU-Micro-Benchmarks/7.2-gompi-2023a-CUDA-12.1.1 %scale=1_node /17289b2f @BotBuildTests:aarch64_nvidia_grace+default
P: bandwidth: 42276.89 MB/s (r:0, l:None, u:None)
[ PASSED ] Ran 18/26 test case(s) from 26 check(s) (0 failure(s), 8 skipped, 0 aborted)
Details
✅ job output file slurm-14067599.out
❌ found message matching ERROR:
✅ no message matching [\s*FAILED\s*].*Ran .* test case

@ocaisa
Copy link
Member

ocaisa commented Sep 18, 2025

This needs special attention for Arm it seems:

== 2025-09-18 15:05:12,506 run.py:502 INFO Running shell command 'make  -j 16 -f Makefile.AVX2.gcc CC="$CC" && rm *.o && make -j 16 -f Makefile.AVX2.PTHREADS.gcc CC="$CC" && rm *.o && make -j 16 -f Makefile.AVX2.HYBRID.gcc CC="$CC"' in /tmp/eessibot/easybuild/build/RAxML/8.2.13/gompi-2023b-avx2/standard-RAxML-8.2.13
== 2025-09-18 15:05:16,218 run.py:613 INFO Output of 'make ...' shell command (stdout + stderr):
rm -f *.o raxmlHPC-AVX2
mpicc -D__SIM_SSE3 -msse3 -D_GNU_SOURCE -O2 -fomit-frame-pointer -funroll-loops -D__AVX    -c -o axml.o axml.c
mpicc -D__SIM_SSE3 -msse3 -D_GNU_SOURCE -O2 -fomit-frame-pointer -funroll-loops -D__AVX    -c -o optimizeModel.o optimizeModel.c
mpicc -D__SIM_SSE3 -msse3 -D_GNU_SOURCE -O2 -fomit-frame-pointer -funroll-loops -D__AVX    -c -o multiple.o multiple.c
mpicc -D__SIM_SSE3 -msse3 -D_GNU_SOURCE -O2 -fomit-frame-pointer -funroll-loops -D__AVX    -c -o searchAlgo.o searchAlgo.c
mpicc -D__SIM_SSE3 -msse3 -D_GNU_SOURCE -O2 -fomit-frame-pointer -funroll-loops -D__AVX    -c -o topologies.o topologies.c
mpicc -D__SIM_SSE3 -msse3 -D_GNU_SOURCE -O2 -fomit-frame-pointer -funroll-loops -D__AVX    -c -o parsePartitions.o parsePartitions.c
mpicc -D__SIM_SSE3 -msse3 -D_GNU_SOURCE -O2 -fomit-frame-pointer -funroll-loops -D__AVX    -c -o treeIO.o treeIO.c
mpicc -D__SIM_SSE3 -msse3 -D_GNU_SOURCE -O2 -fomit-frame-pointer -funroll-loops -D__AVX    -c -o models.o models.c
mpicc -D__SIM_SSE3 -msse3 -D_GNU_SOURCE -O2 -fomit-frame-pointer -funroll-loops -D__AVX    -c -o bipartitionList.o bipartitionList.c
mpicc -D__SIM_SSE3 -msse3 -D_GNU_SOURCE -O2 -fomit-frame-pointer -funroll-loops -D__AVX    -c -o rapidBootstrap.o rapidBootstrap.c
mpicc -D__SIM_SSE3 -msse3 -D_GNU_SOURCE -O2 -fomit-frame-pointer -funroll-loops -D__AVX    -c -o evaluatePartialGenericSpecial.o evaluatePartialGenericSpecial.c
mpicc -D__SIM_SSE3 -msse3 -D_GNU_SOURCE -O2 -fomit-frame-pointer -funroll-loops -D__AVX    -c -o evaluateGenericSpecial.o evaluateGenericSpecial.c
mpicc -D__SIM_SSE3 -msse3 -D_GNU_SOURCE -O2 -fomit-frame-pointer -funroll-loops -D__AVX    -c -o newviewGenericSpecial.o newviewGenericSpecial.c
mpicc -D__SIM_SSE3 -msse3 -D_GNU_SOURCE -O2 -fomit-frame-pointer -funroll-loops -D__AVX    -c -o makenewzGenericSpecial.o makenewzGenericSpecial.c
mpicc -D__SIM_SSE3 -msse3 -D_GNU_SOURCE -O2 -fomit-frame-pointer -funroll-loops -D__AVX    -c -o classify.o classify.c
mpicc -D__SIM_SSE3 -msse3 -D_GNU_SOURCE -O2 -fomit-frame-pointer -funroll-loops -D__AVX  -mavx -c -o fastDNAparsimony.o fastDNAparsimony.c
gcc: error: unrecognized command-line option ‘-msse3’
gcc: error: unrecognized command-line option ‘-msse3’
gcc: error: unrecognized command-line option ‘-msse3’
gcc: error: unrecognized command-line option ‘-msse3’
gcc: error: unrecognized command-line option ‘-msse3’
gcc: error: unrecognized command-line option ‘-msse3’
gcc: error: unrecognized command-line option ‘-msse3’
gcc: error: unrecognized command-line option ‘-msse3’
gcc: error: unrecognized command-line option ‘-msse3’
gcc: error: unrecognized command-line option ‘-msse3’
gcc: error: unrecognized command-line option ‘-msse3’
gcc: error: unrecognized command-line option ‘-msse3’
gcc: error: unrecognized command-line option ‘-msse3’

options:
# see https://github.com/easybuilders/easybuild-easyconfigs/pull/22371
from-commit: 29f82e43229663c22f0c76cb3fc7b6dd5c407cd7
- RAxML-8.2.13-gompi-2023b-avx2.eb
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is not going to work on systems that don't have AVX2, you need to create a variant of https://github.com/easybuilders/easybuild-easyconfigs/blob/develop/easybuild/easyconfigs/r/RAxML/RAxML-8.2.13-gompi-2023a-standard.eb with a newer toolchain

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually, this is a case where I think we should diverge from the "same modules everywhere" goal.

The AVX2 variant of RAxML is definitely worth installing for x86_64 CPUs, but clearly doesn't make any sense for aarch64.

So we should install "fake" modules for the latter, and get them to produce a meaningful error to explain why that installation is not available on aarch64 targets?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think we need to make this exception, we need a better easyconfig. For example, https://github.com/stamatak/standard-RAxML/blob/master/Makefile.HYBRID.gcc has the mechanism to support both x86 and Arm, we should really be using that.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PR for this particular case in easybuilders/easybuild-easyconfigs#23975

RAxML does seem to have some intrinsics available, but the specific code targeted Haswell and hasn't been touched in 10 years, I think a native CPU compilation is a reasonable option

@laraPPr
Copy link
Collaborator

laraPPr commented Sep 23, 2025

This should be closed RAxML was deployed with this pr #1032

@PetrKralCZ PetrKralCZ closed this Sep 23, 2025
@boegel
Copy link
Contributor

boegel commented Sep 23, 2025

This is 2023b toolchain, we don't have this installed yet in EESSI 2023.06

@boegel boegel reopened this Sep 23, 2025
@laraPPr
Copy link
Collaborator

laraPPr commented Sep 23, 2025

Discussion on how to handle this and similar cases see https://gitlab.com/eessi/support/-/issues/196

@ocaisa
Copy link
Member

ocaisa commented Oct 1, 2025

PR opened to make a more universal version of RAxML: easybuilders/easybuild-easyconfigs#23975

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