{2025.06}[foss/2024a] LAMMPS 22Jul2025 with CUDA - #1461
Conversation
|
bot: build repo:eessi.io-2025.06-software instance:eessi-bot-vsc-ugent for:arch=x86_64/amd/zen3,accel=nvidia/cc80 |
|
New job on instance
|
|
bot: build repo:eessi.io-2025.06-software instance:eessi-bot-surf for:arch=x86_64/amd/zen4,accel=nvidia/cc90 |
|
New job on instance
|
|
bot: build repo:eessi.io-2025.06-software instance:eessi-bot-surf for:arch=x86_64/amd/zen4,accel=nvidia/cc90 |
|
New job on instance
|
|
@casparvl why is cuda compute capabilities set like this? LAMMPS does not like it. |
|
bot: build repo:eessi.io-2025.06-software instance:eessi-bot-vsc-ugent for:arch=x86_64/amd/zen3,accel=nvidia/cc80 |
|
New job on instance
|
Because that's the target for which we want CUDA code to be compiled :D If a particular package doesn't support the suffixes in the targets, we should make sure they get stripped. We could do this in an EESSI hook, but it would be better to do it upstream in EasyBuild. Both Note that the |
|
It is because it is not in this mapping, https://github.com/easybuilders/easybuild-easyblocks/blob/ad5538e0d532f06ecdc801794e390db49aa5c350/easybuild/easyblocks/l/lammps.py#L158-L177. From your explanation I see adding 9.0a as an option if building with |
|
We do not build lammps with We add the following mapping in the easyblock or overwrite cuda_cc in the hook. I prefer option 1. |
|
bot: build repo:eessi.io-2025.06-software instance:eessi-bot-surf for:arch=x86_64/amd/zen4,accel=nvidia/cc90 |
|
New job on instance
|
|
bot: build repo:eessi.io-2025.06-software instance:eessi-bot-jsc for:arch=aarch64/nvidia/grace,accel=nvidia/cc90 |
|
New job on instance
|
|
nevermind I have access |
|
Can't get to the build logs so need this before I can continue |
|
bot: build repo:eessi.io-2025.06-software instance:eessi-bot-jsc for:arch=aarch64/nvidia/grace,accel=nvidia/cc90 |
|
New job on instance
|
|
Probably hitting the ARM Neon issues on aarch64 with Kokkos due to CUDA being lower than CUDA 13.1 (or 13.2, which officially fixes the issue)? |
|
New job on instance
|
|
bot: build repo:eessi.io-2025.06-software instance:eessi-bot-mc-aws on:arch=neoverse_v1 for:arch=aarch64/neoverse_v1,accel=nvidia/cc80 |
|
New job on instance
|
|
I have tested it on Julich and it is passing the ctests and sanity check their. For crosscompilation the ctests are failing with: So we should not run the ctests when cross compiling. |
|
bot: build repo:eessi.io-2025.06-software instance:eessi-bot-jsc for:arch=aarch64/nvidia/grace,accel=nvidia/cc90 |
1 similar comment
|
bot: build repo:eessi.io-2025.06-software instance:eessi-bot-jsc for:arch=aarch64/nvidia/grace,accel=nvidia/cc90 |
|
New job on instance
|
|
bot: build repo:eessi.io-2025.06-software instance:eessi-bot-jsc for:arch=aarch64/nvidia/grace,accel=nvidia/cc90 |
|
New job on instance
|
|
This should fail if I have tracked down the correct problem where the hook is now stuck. |
|
New job on instance
|
|
See if build fails because of failing to build containers after mitgation of cve |
|
New job on instance
|
|
Try croscompiling with the new easyblock |
|
New job on instance
|
|
With the LD_PRELOAD added only 3 ctest are failing |
|
bot: build repo:eessi.io-2025.06-software instance:eessi-bot-mc-aws on:arch=zen2 for:arch=x86_64/amd/zen2,accel=nvidia/cc70+nvidia/cc90+nvidia/cc100+nvidia/cc120 |
|
New job on instance
|
|
It is now getting to the sanity check. Setting LD_PRELOAD in the sanity check does not seem to work. However I ran them again because another issue is popping up with the newest easybuild. I think it is related to this change. easybuilders/easybuild-framework#5161. So crosscompiling might be broken for the newest easybuild version @Flamefire do you maybe know what might cause this? |
|
Caspar is attempting to fix this in EESSI/software-layer-scripts#288 |
It's at least not caused by that PR which actually makes it execute |
|
@ocaisa Caspar just left on holiday for a coupld weeks. Should someone else try to pick it up. Or are we gonna leave it until he gets back? |
|
@Flamefire CUDA is demoted to a build dependency in the hooks and we rely on rpath to give us access to the runtime libraries (this avoids having to have a full CUDA installation just to execute CUDA code) |
|
So it is only an EESSI issue, not an EasyBuild issue. |
Loading the module during the sanity check works. In the case of LAMMPS because the tests do not actually use the GPUs if there are non present. If Caspar's work around works not sure. I was just testing it interactively rerunning the tests after loading the CUDA module. |
Uh oh!
There was an error while loading. Please reload this page.