-
Notifications
You must be signed in to change notification settings - Fork 283
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
add requirement for EULA acceptance to CUDA easyblock #3045
Conversation
@boegelbot please test @ generoso EB_ARGS="CUDA-12.1.1.eb" |
@ocaisa: Request for testing this PR well received on login1 PR test command '
Test results coming soon (I hope)... - notification for comment with ID 1833547607 processed Message to humans: this is just bookkeeping information for me, |
Test report by @boegelbot Overview of tested easyconfigs (in order)
Build succeeded for 1 out of 1 (1 easyconfigs in total) |
Urgh, that shouldn't have worked but did because the sources were already on disk. I'll do the reports manually |
Test report by @ocaisa Overview of tested easyconfigs (in order)
Build succeeded for 0 out of 1 (1 easyconfigs in total) |
Ok, that one is the expected failure due to not accepting the EULA (see the gist for the output text) |
Test report by @ocaisa Overview of tested easyconfigs (in order)
Build succeeded for 1 out of 1 (1 easyconfigs in total) |
And that one is with the updated command line:
|
Philosophical question: what does it mean for the software installer to accept the end user license agreement ? |
Are you sure that's not a legal rather than philosophical question? |
My point is that the software installer is not the end user. Merely a middle-person, and that if we consider the EULA for installing the software, it should be considered for using the software (i.e. when the module is loaded, not when the software is installed). |
That's problematic though, as you don't need accept the EULA to run a CUDA application. To be honest, the way we've implemented CUDA support in EESSI this would indeed be possible, we've dropped CUDA to a build dep and rely on RPATH for running the cuda applications. You could require the end user to set a certain environment variable to allow them to load the CUDA module itself. You can do that by configuring an lmod RC file appropriately along the lines of what's done in EESSI/software-layer#381 Unfortunately that's not a global solution though, so I still think this as a reasonable approximation to what is happening a lot in practice. |
I guess we should think of this as a warning to people that CUDA has a EULA, if you make it available you are responsible for making your users aware of that. |
It worked because the bot uses |
Test report by @boegel Overview of tested easyconfigs (in order)
Build succeeded for 1 out of 1 (1 easyconfigs in total) |
No description provided.