Skip to content
This repository was archived by the owner on Apr 4, 2025. It is now read-only.

Commit 6d7094e

Browse files
committed
Disable experimental_spawn_scheduler
Also mark the docker targets for local execution
1 parent f33793a commit 6d7094e

2 files changed

Lines changed: 8 additions & 1 deletion

File tree

‎.bazelrc‎

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -58,7 +58,8 @@ build:remote --jobs=100
5858
# See https://blog.bazel.build/2019/02/01/dynamic-spawn-scheduler.html
5959
# NB: this setting is experimental and can cause obscure build failures.
6060
# The Bazel team does not recommend using this in all projects.
61-
build:remote --experimental_spawn_scheduler
61+
# We can observe failures like Remote connection/protocol failed
62+
# build:remote --experimental_spawn_scheduler
6263

6364
##################################################
6465
# Load any settings specific to the current user.

‎src/BUILD.bazel‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -206,10 +206,16 @@ nodejs_image(
206206
entry_point = "history-server/modules/cli.js",
207207
node_modules = "@history-server_runtime_deps//:node_modules",
208208
templated_args = ["src/prodapp"],
209+
# Actions created by this rule are I/O-bound,
210+
# so there is no benefit to running them remotely
211+
tags = ["local"],
209212
)
210213

211214
container_image(
212215
name = "image",
213216
base = ":nodejs_image",
214217
workdir = "/app/src/nodejs_image.binary.runfiles/angular_bazel_example",
218+
# Actions created by this rule are I/O-bound,
219+
# so there is no benefit to running them remotely
220+
tags = ["local"],
215221
)

0 commit comments

Comments
 (0)