-
Notifications
You must be signed in to change notification settings - Fork 284
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
fix crash in GCC easyblock when cuda-compute-capabilities
EasyBuild configuration option is not set
#3449
Conversation
When no compute capability is set but NVPTX is enabled, trying to figure out the NVPTX architecture fails with the error: ``` File "easybuild/easyblocks/g/gcc.py", line 431, in map_nvptx_capability return sorted_gcc_cc[0] IndexError: list index out of range ``` The error occurs because of an insufficient check for an unset CUDA compute capability. This commit changes the checked conditions, so that empty lists are also correctly handled. Signed-off-by: Jan André Reuter <[email protected]>
Test report by @branfosj Overview of tested easyconfigs (in order)
Build succeeded for 1 out of 1 (1 easyconfigs in total) edit built with no cuda capability set And I've confirmed that this fails without this PR. |
Test report by @branfosj Overview of tested easyconfigs (in order)
Build succeeded for 1 out of 1 (1 easyconfigs in total) edit build with environment variable |
With Test resultBuild succeeded for 1 out of 1 Overview of tested easyconfigs (in order)
Time info
EasyBuild info
Click to open
System infoClick to open
List of loaded modules
EnvironmentClick to open
|
Going in, thanks @Thyre! |
cuda-compute-capabilities
EasyBuild configuration option is not set
This bug will be triggered easily enough that it's a strong incentive for a quick additional bug fix release (EasyBuild v4.9.4), I'll look into that in the coming days. Until then, people who hit this problem can use |
When no compute capability is set but NVPTX is enabled, trying to figure out the NVPTX architecture fails with the error:
The error occurs because of an insufficient check for an unset CUDA compute capability. This commit changes the checked conditions, so that empty lists are also correctly handled.