You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[BUG]: static and bitcode library finders return relative paths #3363
I confirmed there appear to be no duplicate issues for this bug and that I agree to the Code of Conduct.
Type of Bug
Silent Failure
Component
cuda.pathfinder
Describe the bug
find_bitcode_lib() and find_static_lib() document absolute return paths, but return relative paths when a selected search root is relative. The corresponding locate_* results also expose a relative abs_path. Since the find_* functions cache their results, changing the working directory can leave the cached paths pointing to nonexistent files.
I reproduced this on main at commit deb3d040b6d31b8514f19d026c298982c9b6260b. Relative Conda and site-packages roots have the same problem.
How to Reproduce
In a clean Python environment without NVIDIA wheel directories taking precedence, run:
Observed: both returned paths are relative and both exists after chdir values are false.
Expected behavior
Both paths are absolute and still identify the selected files after the working directory changes. Converting a path must also preserve POSIX symlink/.. traversal; lexical normalization before resolving the symlink can point at a different file.
Operating System
Linux aarch64, Python 3.12.3.
nvidia-smi output
Not GPU-dependent; reproduced with CUDA devices hidden.
Activity