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 error test_exclusive_test_and_no_cache_test_results #21994

Open
sgowroji opened this issue Apr 15, 2024 · 0 comments
Open

Bazel CI flaky error test_exclusive_test_and_no_cache_test_results #21994

sgowroji opened this issue Apr 15, 2024 · 0 comments
Assignees
Labels
flaky test team-Remote-Exec Issues and PRs for the Execution (Remote) team type: bug

Comments

@sgowroji
Copy link
Member

sgowroji commented Apr 15, 2024

CI: https://buildkite.com/organizations/bazel/analytics/suites/bazel-bazel/tests/01897295-6b64-7a40-99d3-3818b2e1931b?branch=master

Expected regexp '1 remote cache hit' not found
BAZELCI_TASK=macos
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

Logs:


$TEST_TMPDIR defined: output root default is '/private/var/tmp/_bazel_buildkite/efd671f9e79b13e279a15d2c144e1ba7/sandbox/darwin-sandbox/9051/execroot/_main/_tmp/3f12f3331a664c6c1f307eacd05d84a8' and max_idle_secs default is '15'.
INFO: Invocation ID: 950f0b10-d52e-4075-9446-3f2a43053b53
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 (75 packages loaded, 374 targets configured).
[5 / 6] Testing //a:success_test; 1s remote-cache, processwrapper-sandbox
[5 / 6] Testing //a:success_test; 4s remote-cache, processwrapper-sandbox
INFO: Found 1 test target...
Target //a:success_test up-to-date:
  bazel-bin/a/success_test
INFO: Elapsed time: 5.610s, Critical Path: 4.77s
INFO: 6 processes: 4 internal, 2 processwrapper-sandbox.
INFO: Build completed successfully, 6 total actions
//a:success_test                                                         PASSED in 4.5s

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/efd671f9e79b13e279a15d2c144e1ba7/sandbox/darwin-sandbox/9051/execroot/_main/_tmp/3f12f3331a664c6c1f307eacd05d84a8' 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/efd671f9e79b13e279a15d2c144e1ba7/sandbox/darwin-sandbox/9051/execroot/_main/_tmp/3f12f3331a664c6c1f307eacd05d84a8' and max_idle_secs default is '15'.
INFO: Invocation ID: 8158bf22-77bb-4734-9c65-273723fa6add
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 (75 packages loaded, 374 targets configured).
INFO: Found 1 test target...
Target //a:success_test up-to-date:
  bazel-bin/a/success_test
INFO: Elapsed time: 1.030s, Critical Path: 0.28s
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 remote cache hit' not found.
/private/var/tmp/_bazel_buildkite/efd671f9e79b13e279a15d2c144e1ba7/sandbox/darwin-sandbox/9051/execroot/_main/bazel-out/darwin_x86_64-fastbuild/bin/src/test/shell/bazel/remote/remote_execution_test.runfiles/_main/src/test/shell/bazel/remote/remote_execution_test:2090: in call to test_exclusive_test_and_no_cache_test_results

Tear down:

/private/var/tmp/_bazel_buildkite/efd671f9e79b13e279a15d2c144e1ba7/sandbox/darwin-sandbox/9051/execroot/_main/bazel-out/darwin_x86_64-fastbuild/bin/src/test/shell/bazel/remote/remote_execution_test.runfiles/_main/src/test/shell/bazel/remote/remote_utils.sh: line 47: 80024 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-04-11 07:56:58 (+0000)] Cleaning up workspace

CC Greenteam @meteorcloudy

@sgowroji sgowroji added type: bug breakage team-Local-Exec Issues and PRs for the Execution (Local) team flaky test untriaged labels Apr 15, 2024
@meisterT meisterT added team-Remote-Exec Issues and PRs for the Execution (Remote) team and removed team-Local-Exec Issues and PRs for the Execution (Local) team labels Apr 23, 2024
@tjgq tjgq self-assigned this Apr 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
flaky test team-Remote-Exec Issues and PRs for the Execution (Remote) team type: bug
Projects
None yet
Development

No branches or pull requests

3 participants