clean ${tmpdir} after iterations in install_cuda_and_libraries.sh#814
Conversation
|
Instance
|
|
Instance
|
|
Instance
|
|
bot: build repo:eessi.io-2023.06-software arch:x86_64/generic |
Updates by the bot instance
|
Updates by the bot instance
|
Updates by the bot instance
|
|
New job on instance
|
trz42
left a comment
There was a problem hiding this comment.
Removing the full ${tmpdir} inside the loop likely lets the script fail if one processes multiple easystack files. However, the tmpdir directory is only needed for each loop iteration, so we don't need to wait with the clean up until the loop has processed all easystack files.
…ftware-layer into eessi-2023.06-fix-clean-up-dir-install_cuda_and_libraries.sh
1f6487e to
66c36c8
Compare
|
bot: build repo:eessi.io-2023.06-software arch:x86_64/generic |
Updates by the bot instance
|
Updates by the bot instance
|
Updates by the bot instance
|
|
New job on instance
|
|
Label |
|
PR merged! Moved |
|
PR merged! Moved |
|
PR merged! Moved |
| # clean up tmpdir | ||
| rm -rf "${tmpdir}" | ||
| # clean up tmpdir content | ||
| rm -rf "${tmpdir}"/* |
There was a problem hiding this comment.
Shouldn't we then remove ${tmpdir} after the loop?
There was a problem hiding this comment.
Yes, but that approach only removes the contents of $tmpdir, never $tmpdir itself. This can be done outside the loop, see #816
The
${tmpdir}can be cleaned after all iterations are done when having multipleeasystacks/eessi-*CUDA*.ymlfiles