Apply hooks in install_cuda_and_libraries#165
Conversation
…at the directory check is skipped, as we INTEND to install in an exceptional (i.e. non-accelerator) path
|
bot: build repo:eessi.io-2023.06-software instance:eessi-bot-deucalion for:arch=aarch64/a64fx |
|
New job on instance
|
|
New job on instance
|
|
@casparvl This looks fine to me, can you confirm here that it works in real life |
| # Store MODULEPATH so it can be restored at the end of each loop iteration | ||
| SAVE_MODULEPATH=${MODULEPATH} | ||
|
|
||
| for EASYSTACK_FILE in ${TOPDIR}/easystacks/eessi-*CUDA*.yml; do |
There was a problem hiding this comment.
Don't know how you managed to get this to work, that path is not correct...
There was a problem hiding this comment.
Should be
${TOPDIR}/easystacks/${EESSI_VERSION}/eessi-*CUDA*.yml
(I think)
Make sure the hooks are applied in install_cuda_and_libraries, but that the directory check is skipped, as we INTEND to install in an exceptional (i.e. non-accelerator) path.
This solves an issue I had running
install_cuda_and_libraries.shon an H100 system. It would cause the CUDA sanity check to fail since the hooks weren't being applied that would turn the9.0aCC into a9.0.Originally, we skipped the hooks alltogether. But the real solution is to apply the hooks, but make sure that the hook that does the installation path check is skipped.