{2025.06}[SYSTEM] CUDA 12.6.0,12.8.0, cuDNN 9.5.0.50,9.10.1.4 #1351
+16
−1
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
December 24, 2025 17:39
…if we can get it to work
casparvl
added
the
2025.06-software.eessi.io
This was referenced Jan 5, 2026
casparvl
changed the title
Collaborator
Author
|
Let's first try this for a single CPU arch for each supported CC. Native builds: bot: build repo:eessi.io-2025.06-software instance:eessi-bot-surf for:arch=x86_64/intel/icelake,accel=nvidia/cc80 Cross compiles: bot: build repo:eessi.io-2025.06-software instance:eessi-bot-mc-aws on:arch=zen4 for:arch=x86_64/amd/zen4,accel=nvidia/cc100 |
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
Collaborator
|
bot: help |
Updates by the bot instance
|
Updates by the bot instance
|
Updates by the bot instance
|
Updates by the bot instance
|
Updates by the bot instance
|
Updates by the bot instance
|
Collaborator
|
bot: help |
Updates by the bot instance
|
Updates by the bot instance
|
Updates by the bot instance
|
Updates by the bot instance
|
Updates by the bot instance
|
Updates by the bot instance
|
Collaborator
Author
|
So... the updated hooks are not picked up, because they were used from the repository ( 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
|
|
This is the status of all the
|
Collaborator
|
bot: build repo:eessi.io-2025.06-software instance:eessi-bot-rug for:arch=x86_64/intel/skylake_avx512,accel=nvidia/cc70 |
|
New job on instance
|
Collaborator
Author
|
FYI: we should hold off on deploying this until we've resolved EESSI/compatibility-layer#226 Edit: i.e. essentially, that should be done by deploying EESSI/compatibility-layer#227 , but building that with the bot proves problematic. |
Collaborator
Author
|
bot:status last_build |
|
This is the status of all the
|
|
This is the status of all the
|
|
This is the status of all the
|
2 similar comments
|
This is the status of all the
|
|
This is the status of all the
|
Collaborator
Author
|
bot:show_config |
|
Instance
|
|
Instance
|
|
Instance
|
|
Instance
|
|
Instance
|
Collaborator
Author
|
bot:show_config |
|
Instance
|
|
Instance
|
|
Instance
|
|
Instance
|
|
Instance
|
|
Instance
|
Collaborator
Author
|
bot:status last_build |
|
This is the status of all the
|
|
This is the status of all the
|
1 similar comment
|
This is the status of all the
|
|
This is the status of all the
|
2 similar comments
|
This is the status of all the
|
|
This is the status of all the
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Many things still need to be done... The software-layer-scripts PR should make sure to
--module-onlyif they target CC100 or above9.5.0comes, I think, only with9.0device code, not9.0a. Thus, we should change the requested CC to9.0for that particular software name & version. For cuDNN 9.10.1.4, I think9.0ais supported, but10.0fis not and it should be changed to10.0. I'd prefer to make those changes in hooks to avoid having to open multiple different software-layer PR, each with customoptionsfor the build. Added advantage is that by doing it in the hooks, it also fixes things forEESSI-extend-based installations.Edit 08-01:
cuDNN-9.5.0.50indeed contains device code for7.0,8.0and9.0, but not for9.0a, which causes the sanity check to fail. So we should make a conversion from 9.0a to 9.0 (in a hook?) for this version.cuDNN-9.10.1.4contains device code for7.0,8.0,9.0a,10.0,12.0, but not for10.0fand12.0f, so needs stripping of the suffix for those as well.This PR should replace #1278 , #1286 and #1287