{2025.06}[SYSTEM] Cuda 12.6.0, 12.8.0, cuDNN 9.5.0.50 #1278
Conversation
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
added 2 commits
October 30, 2025 13:42
Collaborator
Author
|
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
|
added 2 commits
October 30, 2025 14:12
Collaborator
Author
|
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
|
Collaborator
Author
|
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
|
Collaborator
Author
|
Failure in the cuDNN host injections installations because it doesn't contain ptx code (fixed in EESSI/software-layer-scripts@e25b625 en bf2fc9c) Also, another failure: Not sure what's wrong here. We may be missing a |
Collaborator
Author
|
Added some extra verbosity EESSI/software-layer-scripts@54bd9ad , let's see 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
|
Collaborator
Author
|
Making it verbose seems to have solved the issue. That is, of course, impossible, but... things are working now: So maybe this was just one more of |
Collaborator
Author
|
Let's get all of those host-injections installed... All bots that run native builds (one architecture per bot is sufficient) bot: build repo:eessi.io-2025.06-software instance:eessi-bot-vsc-ugent for:arch=x86_64/intel/cascadelake,accel=nvidia/cc70 x86_64 and arm archs on AWS bot: 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
|
|
New job on instance
|
casparvl
added
2025.06-software.eessi.io
Collaborator
Author
|
Edit: not sure why the previous build failed. The installations in the host_injections failed with a message that the lock file was already present. That's very strange, there should not be a lock file in the host_injections... 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
|
Collaborator
Author
|
Oh crap, I see the issue, the other build was bot: build repo:eessi.io-2023.06-software instance:eessi-bot-mc-aws for:arch=aarch64/generic |
|
New job on instance
|
Collaborator
Author
|
bot: build repo:eessi.io-2023.06-software instance:eessi-bot-mc-aws for:arch=aarch64/generic |
|
New job on instance
|
Collaborator
Author
|
Wrong version... bot: build repo:eessi.io-2025.06-software instance:eessi-bot-mc-aws for:arch=aarch64/generic |
Collaborator
|
Weird |
Collaborator
Author
|
That seems completely unrelated to the update to the software-layer-scripts EESSI/software-layer-scripts#124 . I seem to vaguely remember you had this issue before, no? |
Collaborator
|
This seem a fluke on github site no? |
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
|
Collaborator
|
Or a problem on the node where it ran |
Collaborator
|
bot: build repo:eessi.io-2023.06-software instance:eessi-bot-vsc-ugent for:arch=x86_64/amd/zen3,accel=nvidia/cc80 |
|
New job on instance
|
Collaborator
|
Ok so the tests seem to be fine I don't know what is going wrong with clone on our Cascadelake cluster today. |
Collaborator
Author
|
Ok, I'll try this once more, in order to test updates from EESSI/software-layer-scripts#124 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
|
Collaborator
|
We opened an issue for the git clone problem, EESSI/compatibility-layer#232. Maybe @bedroge can have a look. |
Collaborator
Author
|
bot:status last_build |
|
This is the status of all the
|
4 similar comments
|
This is the status of all the
|
|
This is the status of all the
|
|
This is the status of all the
|
|
This is the status of all the
|
Collaborator
Author
|
Interesting, I guess we're exceeding some length with the |
Collaborator
Author
|
bot: build repo:eessi.io-2025.06-software instance:eessi-bot-mc-aws on:arch=zen2 for:arch=x86_64/amd/zen2,accel=nvidia/cc100 |
|
New job on instance
|
Collaborator
Author
|
Ooof, seems that EasyBuild does a hard check on the format of the |
Collaborator
Author
|
Hm, this surprised me, because I tried This will require a framework change I think :( |
Contributor
Please open a PR for this ASAP. An EasyBuild release is way overdue, so I'll be closing the window of opportunity to get changes in that can be included in EasyBuild v5.2.0 very soon... Seems like accepting |
Collaborator
|
Collaborator
Author
|
And now we wait for EB 5.2.0 :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
I think we should deploy the script from EESSI/software-layer-scripts#120 through this current PR, then change the
build.shback to it's original form. The issue is that EESSI/software-layer-scripts#120 can't be deployed there, because no software is built, and thus no "no missing installations" message is printed. This causes the bot to consider the build step a 'failure'.