no need to set --remote_timeout

6 years ago · 65b184d30a
parent 79cfdb525c
commit 65b184d30a
2 changed files with 0 additions and 2 deletions
--- a/tools/remote_build/rbe_common.bazelrc
+++ b/tools/remote_build/rbe_common.bazelrc
@ -30,7 +30,6 @@ build --spawn_strategy=remote
 build --strategy=Javac=remote
 build --strategy=Closure=remote
 build --genrule_strategy=remote
-build --remote_timeout=7200  # the theory is that this needs to be bigger than max test_timeout otherwise you can get weird "Unevaluated target" errors

 build --remote_instance_name=projects/grpc-testing/instances/default_instance

--- a/tools/remote_build/windows.bazelrc
+++ b/tools/remote_build/windows.bazelrc
@ -24,7 +24,6 @@ build --spawn_strategy=remote
 build --strategy=Javac=remote
 build --strategy=Closure=remote
 build --genrule_strategy=remote
-build --remote_timeout=7200  # the theory is that this needs to be bigger than max test_timeout otherwise you can get weird "Unevaluated target" errors

 build --remote_instance_name=projects/grpc-testing/instances/grpc-windows-rbe-test