-
Notifications
You must be signed in to change notification settings - Fork 16
fix typo in EESSI-extend + install CUDA in host injections earlier in the software install scripts (+ deploy EESSI-extend/2025.06)
#54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
bot: build repo:eessi.io-2023.06-software instance:eessi-bot-mc-aws arch:zen2 |
|
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
|
|
Unfortunately we cannot build for a64fx, this will then be dangerously out of sync! |
|
The error being reported is now to find out why... EDIT: A CUDA check somewhere is reverting to EB 4.9.4 which is causing the problem. We can sidestep it by unloading the module after a successful install |
|
Looks like it's using an old version of EB for this installation: edit: ah, you just found that too :-) |
Since in 2023.06 it relies on EB 4
|
bot: build repo:eessi.io-2023.06-software instance:eessi-bot-mc-aws arch:zen2 |
|
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
|
|
bot: build repo:eessi.io-2025.06-software instance:eessi-bot-mc-aws arch:zen2 |
EESSI-extend + install CUDA in host injections earlier in the software install scripts (+ deploy)EESSI-extend + install CUDA in host injections earlier in the software install scripts (+ deploy EESSI-extend/2025.06)
|
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
|
|
Can we hold off on this for a moment until we can manually ingest the tarballs from #59? That way we can see how well it performs then. The deployment of that PR is already underway (it's just a lot of data to move around) |
|
Sorry for the delay, from my side feel free to go ahead and deploy if you wish! 👍 |
|
@Neves-P This PR contains tarballs for both I'm guessing those should be handled through separate For now, I only see a staging PR for the edit: nevermind, |
…I#54. This will make sure the rebuild of EESSI-extend is done before building the CUDA in host-injections. That's essentially, as the fix in EESSI-extend is needed to make the CUDA in host-injections step pass
Proper fix for this is in #66 |
#45 Was not actually deployed