{2025.06}[foss-2024a] Siesta 5.4.2 CUDA 12.6.0#1506
Open
AnthoniAlcaraz wants to merge 2 commits into
Open
Conversation
Contributor
|
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
|
Contributor
|
test step is failing: It's not fully clear to me why though, looks like it could be a segfault ( @casparvl Any ideas? |
Contributor
|
bot: build repo:eessi.io-2025.06-software instance:eessi-bot-jsc for:arch=aarch64/nvidia/grace,accel=nvidia/cc90 |
|
New job on instance
|
Collaborator
|
I can see the same error on local build for aarch64/nvidia/grace/cc90 |
Contributor
@TopRichard Is that manually, with (just) I also tried on a Grace Hopper node manually with The |
Collaborator
That is manually using the |
Contributor
|
The problem did not occur when testing with the build bot @ JSC, so the mystery continues... Hoping to hear back from @casparvl on the test @ SURF |
Collaborator
There seems to be a weird issue with the Surf bot, the job ran out of memory: The same happened to a GROMACS+CUDA build job in #1482 and a LAMMPS+CUDA build job in #1461 (comment). |
laraPPr
added
the
issue: build cluster
Collaborator
|
The issue with the Surf bot has been resolved, let's try again 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
|
Collaborator
|
Pointing to the sif file now in repos.cfg. Let's see if that also fixes UGent. |
Collaborator
|
@casparvl this is why the test-suite is failing at UGent |
Collaborator
|
Stupid wrong repo |
|
New job on instance
|
|
New job on instance
|
Collaborator
|
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
|
Collaborator
|
bot: build repo:eessi.io-2025.06-software instance:eessi-bot-vsc-ugent for:arch=x86_64/intel/cascadelake,accel=nvidia/cc70 |
|
New job on instance
|
laraPPr
removed
the
issue: build cluster
Collaborator
|
bot: build repo:eessi.io-2025.06-software instance:eessi-bot-surf for:arch=x86_64/intel/icelake,accel=nvidia/cc80 |
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
Collaborator
|
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 |
|
New job on instance
|
|
New job on instance
|
Unable to download or merge changes between the source branch and the destination branch. |
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
Unable to download or merge changes between the source branch and the destination branch. |
Collaborator
|
Collaborator
|
@AnthoniAlcaraz We have now compiled all the native GPU builds for siesta. We ran into trouble with the crosscompiling. We see that the tests are failing. Do you know if those tests are expecting their to be an actual GPU available? |
Author
Hi Lara, yes, if an NVIDIA GPU is detected on the node, the tests should run without issues. The failures you're seeing are expected when building on a node without a GPU available and the building and compilation include the usage of a GPU. can we see the content of |
Collaborator
|
yes , here they are. They all fail because it does a cuda_getdevicecount. So I'm guessing we should skip those ctests on the crosscompiled nodes. Maybe something like with did for lammps for everything but the native targets. https://github.com/EESSI/software-layer-scripts/blob/9aa5e0a9abf247d4bd16e720532e05a1fee4d9e7/eb_hooks.py#L1559 |
Contributor
|
@laraPPr It definitely makes sense to me to skip any GPU tests if they expect to actually find a GPU (rather than passing or being skipped automatically). So we can basically run |
Contributor
|
Rather than poking |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
Adding the latest SIESTA version with CUDA