Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bazel CI flaky src.test.shell.bazel.remote.remote_execution_test test_exclusive_test_and_no_cache_test_resultsTear #22938

Open
sgowroji opened this issue Jul 3, 2024 · 0 comments
Labels
breakage flaky test team-Remote-Exec Issues and PRs for the Execution (Remote) team type: bug

Comments

@sgowroji
Copy link
Member

sgowroji commented Jul 3, 2024

CI: https://buildkite.com/bazel/bazel-bazel/builds/28484#0190747d-2695-402a-a302-f8ed98047385

Platform: MacOS

Logs:

FAIL: �[0m//src/test/shell/bazel/remote:remote_execution_test (shard 2 of 5) 
$TEST_TMPDIR defined: output root default is '/private/var/tmp/_bazel_buildkite/4f2d8053f9dbbed2b4cd2fdc6fb27365/sandbox/darwin-sandbox/9052/execroot/_main/_tmp/ee9047f7e54192d1c96723be06c02001' and max_idle_secs default is '15'.
INFO: Invocation ID: 6d7aaa9a-cf49-4374-b6aa-e686a3ca315b
ERROR: Failed to query remote execution capabilities: UNIMPLEMENTED: Method not found: build.bazel.remote.execution.v2.Capabilities/GetCapabilities
Computing main repo mapping: 
Loading: 
Loading: 0 packages loaded
Analyzing: target //a:success_test (1 packages loaded, 0 targets configured)
Analyzing: target //a:success_test (1 packages loaded, 0 targets configured)
[0 / 1] [Prepa] BazelWorkspaceStatusAction stable-status.txt
INFO: Analyzed target //a:success_test (88 packages loaded, 405 targets configured).
WARNING: Remote Cache: UNIMPLEMENTED: Method not found: build.bazel.remote.execution.v2.Capabilities/GetCapabilities
INFO: Found 1 test target...
Target //a:success_test up-to-date:
  bazel-bin/a/success_test
INFO: Elapsed time: 0.793s, Critical Path: 0.23s
INFO: 6 processes: 4 internal, 2 processwrapper-sandbox.
INFO: Build completed successfully, 6 total actions
//a:success_test                                                         PASSED in 0.2s

Executed 1 out of 1 test: 1 test passes.
There were tests whose specified size is too big. Use the --test_verbose_timeout_warnings command line option to see which ones these are.
$TEST_TMPDIR defined: output root default is '/private/var/tmp/_bazel_buildkite/4f2d8053f9dbbed2b4cd2fdc6fb27365/sandbox/darwin-sandbox/9052/execroot/_main/_tmp/ee9047f7e54192d1c96723be06c02001' 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 log: -----------------------------------------------------------
$TEST_TMPDIR defined: output root default is '/private/var/tmp/_bazel_buildkite/4f2d8053f9dbbed2b4cd2fdc6fb27365/sandbox/darwin-sandbox/9052/execroot/_main/_tmp/ee9047f7e54192d1c96723be06c02001' and max_idle_secs default is '15'.
INFO: Invocation ID: ed7d5dac-178e-4032-9c43-c1b9dd02c4b2
ERROR: Failed to query remote execution capabilities: UNIMPLEMENTED: Method not found: build.bazel.remote.execution.v2.Capabilities/GetCapabilities
Computing main repo mapping: 
Loading: 
Loading: 0 packages loaded
Analyzing: target //a:success_test (1 packages loaded, 0 targets configured)
Analyzing: target //a:success_test (1 packages loaded, 0 targets configured)
[0 / 1] [Prepa] BazelWorkspaceStatusAction stable-status.txt
INFO: Analyzed target //a:success_test (88 packages loaded, 405 targets configured).
WARNING: Remote Cache: UNIMPLEMENTED: Method not found: build.bazel.remote.execution.v2.Capabilities/GetCapabilities
INFO: Found 1 test target...
Target //a:success_test up-to-date:
  bazel-bin/a/success_test
INFO: Elapsed time: 0.674s, Critical Path: 0.11s
INFO: 6 processes: 4 internal, 2 processwrapper-sandbox.
INFO: Build completed successfully, 6 total actions
//a:success_test                                                         PASSED in 0.1s

Executed 1 out of 1 test: 1 test passes.
There were tests whose specified size is too big. Use the --test_verbose_timeout_warnings command line option to see which ones these are.
------------------------------------------------------------------------
test_exclusive_test_and_no_cache_test_results FAILED: Expected regexp '1.*-sandbox' not found.
/private/var/tmp/_bazel_buildkite/4f2d8053f9dbbed2b4cd2fdc6fb27365/sandbox/darwin-sandbox/9052/execroot/_main/bazel-out/darwin_arm64-fastbuild/bin/src/test/shell/bazel/remote/remote_execution_test.runfiles/_main/src/test/shell/bazel/remote/remote_execution_test:2088: in call to test_exclusive_test_and_no_cache_test_results

Test Details:

Expected regexp '1.*-sandbox' not found BAZELCI_TASK=macos_arm64 TEST_TARGET=//src/test/shell/bazel/remote:remote_execution_test TEST_NAME=test_exclusive_test_and_no_cache_test_results  bazel test //src/test/shell/bazel/remote:remote_execution_test --test_filter=test_exclusive_test_and_no_cache_test_results 

CC Greenteam @meteorcloudy

@sgowroji sgowroji added type: bug breakage team-Remote-Exec Issues and PRs for the Execution (Remote) team flaky test labels Jul 3, 2024
@sgowroji sgowroji changed the title Bazel CI flaky src.test.shell.bazel.remote.remote_execution_test test_exclusive_test_and_no_cache_test_results Tear down: /private/var/tmp/_bazel_buildkite/4f2d8053f9dbbed2b4cd2fdc6fb27365/sandbox/darwin-sandbox/9052/execroot/_main/bazel-out/darwin_arm64-fastbuild/bin/src/test/shell/bazel/remote/remote_execution_test.runfiles/_main/src/test/shell/bazel/remote/remote_utils.sh: line 47: 42280 Killed: 9 "${REMOTE_WORKER}" --singlejar --jvm_flag=-Djava.library.path="${native_lib}" --work_path="${work_path}" --cas_path="${cas_path}" --listen_port=${worker_port} --pid_file="${pid_file}" "$@" >&$TEST_log INFO[remote_execution_test 2024-07-02 17:47:13 (+0000)] Cleaning up workspace Bazel CI flaky src.test.shell.bazel.remote.remote_execution_test test_exclusive_test_and_no_cache_test_resultsTear Jul 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breakage flaky test team-Remote-Exec Issues and PRs for the Execution (Remote) team type: bug
Projects
None yet
Development

No branches or pull requests

1 participant