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
When testing //src/test/shell/bazel/remote:remote_execution_test, we saw that the setup and tear_down methods both seem to be broken:
test_fail FAILED: Timed out waiting for remote worker to start. .
/usr/local/google/home/twerth/.cache/bazel/_bazel_twerth/f01bc937da326f5bb0feb15c854c110c/sandbox/linux-sandbox/1546/execroot/io_bazel/bazel-out/k8-fastbuild/bin/src/test/shell/bazel/remote/remote_execution_test.runfiles/io_bazel/src/test/shell/bazel/remote/remote_utils.sh:41: in call to start_worker
/usr/local/google/home/twerth/.cache/bazel/_bazel_twerth/f01bc937da326f5bb0feb15c854c110c/sandbox/linux-sandbox/1546/execroot/io_bazel/bazel-out/k8-fastbuild/bin/src/test/shell/bazel/remote/remote_execution_test.runfiles/io_bazel/src/test/shell/bazel/remote/remote_execution_test:49: in call to set_up
INFO[remote_execution_test 2020-10-28 15:54:28 (+0000)] Cleaning up workspace
-- Test log: -----------------------------------------------------------
$TEST_TMPDIR defined: output root default is '/usr/local/google/home/twerth/.cache/bazel/_bazel_twerth/f01bc937da326f5bb0feb15c854c110c/sandbox/linux-sandbox/1546/execroot/io_bazel/_tmp/e29069609bc298cb3b1996e685786dd3' and max_idle_secs default is '15'.
Extracting Bazel installation...
Starting local Bazel server and connecting to it...
INFO: Starting clean (this may take a while). Consider using --async if the clean takes more than several minutes.
$TEST_TMPDIR defined: output root default is '/usr/local/google/home/twerth/.cache/bazel/_bazel_twerth/f01bc937da326f5bb0feb15c854c110c/sandbox/linux-sandbox/1546/execroot/io_bazel/_tmp/e29069609bc298cb3b1996e685786dd3' and max_idle_secs default is '15'.
INFO: Starting clean (this may take a while). Consider using --async if the clean takes more than several minutes.
------------------------------------------------------------------------
test_fail FAILED: terminated because this command returned a non-zero status:
/usr/local/google/home/twerth/.cache/bazel/_bazel_twerth/f01bc937da326f5bb0feb15c854c110c/sandbox/linux-sandbox/1546/execroot/io_bazel/bazel-out/k8-fastbuild/bin/src/test/shell/bazel/remote/remote_execution_test.runfiles/io_bazel/src/test/shell/bazel/remote/remote_execution_test:2272: in call to main
/usr/local/google/home/twerth/.cache/bazel/_bazel_twerth/f01bc937da326f5bb0feb15c854c110c/sandbox/linux-sandbox/1546/execroot/io_bazel/bazel-out/k8-fastbuild/bin/src/test/shell/bazel/remote/remote_execution_test.runfiles/io_bazel/src/test/shell/bazel/remote/remote_utils.sh: line 46: pid_file: unbound variable
$TEST_TMPDIR defined: output root default is '/usr/local/google/home/twerth/.cache/bazel/_bazel_twerth/f01bc937da326f5bb0feb15c854c110c/sandbox/linux-sandbox/1546/execroot/io_bazel/_tmp/e29069609bc298cb3b1996e685786dd3' and max_idle_secs default is '15'.
Notice the timeout in the first line and the unbound variable in one of the last lines.
Seems to happen with released Bazel and Bazel at HEAD on both Linux and Mac.
The text was updated successfully, but these errors were encountered:
The stop_worker function in remote_utils.sh was broken with an unbounded
variable error. This error somehow shadowed the return code of the test
cases on macOS.
Fixesbazelbuild#12377Fixesbazelbuild#12376
The stop_worker function in remote_utils.sh was broken with an unbounded
variable error. This error somehow shadowed the return code of the test
cases on macOS.
Fixesbazelbuild#12377Fixesbazelbuild#12376
Description of the problem / feature request:
When testing
//src/test/shell/bazel/remote:remote_execution_test
, we saw that the setup and tear_down methods both seem to be broken:Notice the timeout in the first line and the unbound variable in one of the last lines.
Seems to happen with released Bazel and Bazel at HEAD on both Linux and Mac.
The text was updated successfully, but these errors were encountered: