bazelbuild / bazelbuild/bazel

Bazel CI Flaky src.test.shell.bazel.bazel_workspace_status_test test_workspace_status_parameters

Open
#20,314 0 comments 0 reactions 0 assignees View on GitHub
flaky test P2 team-ExternalDeps type: bug
Dominant language
Java
Stars
25.8k
Forks
4.6k
Avg merge
2d 20h
Merged PRs (30d)
72

Description

**Reference** : [https://buildkite.com/organizations/bazel/analytics/suites/bazel-bazel/tests/0188440b-e042-74e4-8cb7-edd02d2ee638](https://buildkite.com/organizations/bazel/analytics/suites/bazel-bazel/tests/0188440b-e042-74e4-8cb7-edd02d2ee638)

**Test Details :**

BAZELCI\_TASK=ubuntu2204 TEST\_TARGET=//src/test/shell/bazel:bazel\_workspace\_status\_test TEST\_NAME=test\_workspace\_status\_parameters 

bazel test //src/test/shell/bazel:bazel\_workspace\_status\_test --test\_filter=test\_workspace\_status\_parameters 
 

**Logs**:

```

$TEST_TMPDIR defined: output root default is '/var/lib/buildkite-agent/.cache/bazel/_bazel_buildkite-agent/ec321eb2cc2d0f8f91b676b6d4c66c29/sandbox/linux-sandbox/8349/execroot/_main/_tmp/870516d85d89aaa3d57b8d2a4d60445a' and max_idle_secs default is '15'.
Starting local Bazel server and connecting to it...
Computing main repo mapping:
WARNING: --enable_bzlmod is set, but no MODULE.bazel file was found at the workspace root. Bazel will create an empty MODULE.bazel file. Please consider migrating your external dependencies from WORKSPACE to MODULE.bazel. For more details, please refer to https://github.com/bazelbuild/bazel/issues/18958.
Computing main repo mapping:
Computing main repo mapping:
Loading:
Loading: 0 packages loaded
Analyzing: target //a:a (1 packages loaded, 0 targets configured)
Analyzing: target //a:a (1 packages loaded, 0 targets configured)
[0 / 1] [Prepa] BazelWorkspaceStatusAction stable-status.txt
INFO: Analyzed target //a:a (5 packages loaded, 7 targets configured).
[1 / 2] [Prepa] Executing genrule //a:a
WARNING: Both hermetic '/tmp' and an explicit tmpfs mount on '/tmp' is requested, using tmpfs
INFO: Found 1 target...
Target //a:a up-to-date:
bazel-bin/a/a.out
INFO: Elapsed time: 12.920s, Critical Path: 0.36s
INFO: 2 processes: 1 internal, 1 linux-sandbox.
INFO: Build completed successfully, 2 total actions
INFO[bazel_workspace_status_test 2023-11-22 13:01:50 (+0000)] Cleaning up workspace
-- Test log: -----------------------------------------------------------
$TEST_TMPDIR defined: output root default is '/var/lib/buildkite-agent/.cache/bazel/_bazel_buildkite-agent/ec321eb2cc2d0f8f91b676b6d4c66c29/sandbox/linux-sandbox/8349/execroot/_main/_tmp/870516d85d89aaa3d57b8d2a4d60445a' and max_idle_secs default is '15'.

Server terminated abruptly (error code: 14, error message: 'failed to connect to all addresses; last error: UNKNOWN: Failed to connect to remote host: Connection refused', log file: '/var/lib/buildkite-agent/.cache/bazel/_bazel_buildkite-agent/ec321eb2cc2d0f8f91b676b6d4c66c29/sandbox/linux-sandbox/8349/execroot/_main/_tmp/870516d85d89aaa3d57b8d2a4d60445a/root/774ff95446193d1c962667b795fdb4fa/server/jvm.out')

------------------------------------------------------------------------
test_workspace_status_parameters FAILED: terminated because this command returned a non-zero status:
/var/lib/buildkite-agent/.cache/bazel/_bazel_buildkite-agent/ec321eb2cc2d0f8f91b676b6d4c66c29/sandbox/linux-sandbox/8349/execroot/_main/bazel-out/k8-fastbuild/bin/src/test/shell/bazel/bazel_workspace_status_test.runfiles/_main/src/test/shell/testenv.sh:721: in call to cleanup_workspace
/var/lib/buildkite-agent/.cache/bazel/_bazel_buildkite-agent/ec321eb2cc2d0f8f91b676b6d4c66c29/sandbox/linux-sandbox/8349/execroot/_main/bazel-out/k8-fastbuild/bin/src/test/shell/bazel/bazel_workspace_status_test.runfiles/_main/src/test/shell/testenv.sh:741: in call to testenv_tear_down
```

CC **Greenteam** @fweikert

Contributor guide

Open the contributing guide

Research direction

Start by rerunning the command for //src/test/shell/bazel:bazel_workspace_status_test with --test_filter=test_workspace_status_parameters and inspect the failure around cleanup_workspace in testenv.sh. Trace the server termination reported in the log, then verify that the test completes successfully without cleanup_workspace returning a non-zero status.

Written by the indexing model from the issue text.

Assessment

Tech stack
shell
Domain
build-system, ci-cd, testing
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.