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
Description of the problem / feature request / question:
I’m trying to use remote workers, but it seems like runfiles for the tools (a py_binary defined in the same workspace) are not shipped to remote workers.
# bazel --host_jvm_args=-Dbazel.DigestFunction=SHA1 build --spawn_strategy=remote --hazelcast_node=127.0.0.1:5701 --remote_worker=127.0.0.1:8080 :gen
INFO: Found 1 target...
ERROR: /tmp/repro/BUILD:2:1: Executing genrule //:gen failed: com.google.devtools.build.lib.shell.BadExitStatusException: Process exited with status 1.
Traceback (most recent call last):
File "bazel-out/host/bin/hello", line 140, in <module>
Main()
File "bazel-out/host/bin/hello", line 90, in Main
module_space = FindModuleSpace()
File "bazel-out/host/bin/hello", line 71, in FindModuleSpace
sys.argv[0])
AssertionError: Cannot find .runfiles directory for bazel-out/host/bin/hello
Target //:gen failed to build
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 3.678s, Critical Path: 0.60s
Description of the problem / feature request / question:
I’m trying to use remote workers, but it seems like runfiles for the tools (a py_binary defined in the same workspace) are not shipped to remote workers.
cc @hhclam (thanks for your work on this!)
If possible, provide a minimal example to reproduce the problem:
…so, the BUILD file works as expected.
Now, in a separate terminal, start a remote worker:
…then, try to build remotely:
Environment info
bazel info release
):The text was updated successfully, but these errors were encountered: