-
Notifications
You must be signed in to change notification settings - Fork 213
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
Make remote-mqpu auto-launcher aware of CUDAQ_DYNLIBS env var #2385
Conversation
Signed-off-by: Ben Howe <[email protected]>
Signed-off-by: Ben Howe <[email protected]>
CUDA Quantum Docs Bot: A preview of the documentation can be found here. |
CUDA Quantum Docs Bot: A preview of the documentation can be found here. |
Signed-off-by: Bettina Heim <[email protected]>
Signed-off-by: Bettina Heim <[email protected]>
Command Bot: Processing... |
Signed-off-by: Bettina Heim <[email protected]>
Command Bot: Processing... |
Signed-off-by: Bettina Heim <[email protected]>
Command Bot: Processing... |
CUDA Quantum Docs Bot: A preview of the documentation can be found here. |
Note that testing this change fully requires a GPU runner, and hence will only happen post-merge as far as the pipelines are concerned (hence the failing codecov check). |
CUDA Quantum Docs Bot: A preview of the documentation can be found here. |
Signed-off-by: Ben Howe <[email protected]> Signed-off-by: Bettina Heim <[email protected]> Co-authored-by: Bettina Heim <[email protected]>
If auto-launch is used from a Python environment, it is aware of where the custatevec and cutensornet libs are through the CUDAQ_DYNLIBS environment variable, but it was counting on the LD_LIBRARY_PATH to find them instead. This updates the logic to use the CUDAQ_DYNLIBS if the environment variable is present.