The local gen_build_info rule calls into find_cuda_config, which only works in the remote image. This is additionally brittle: relying on TF_CUDA_VERSION being an action_env is poisoning our caches, and running find_cuda_conifg multiple times is bugprone. I think the better way to do this is to put the information from the repo_rule into a file template as part of the repo rule configuration (cuda_configure.bzl). Then we can just include that file, instead of trying to do that as part of the action. PiperOrigin-RevId: 311148754 Change-Id: I80daa8652a85b2a1897c15117e6422bfd21cee6a
0 lines
Python
0 lines
Python