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 __main__.BazelExternalRepositoryTest testNewHttpTarArchiveWithSymlinks #21993

Open
sgowroji opened this issue Apr 15, 2024 · 1 comment
Labels
breakage flaky test P2 We'll consider working on this in future. (Assignee optional) team-ExternalDeps External dependency handling, remote repositiories, WORKSPACE file. type: bug

Comments

@sgowroji
Copy link
Member

sgowroji commented Apr 15, 2024

CI: https://buildkite.com/organizations/bazel/analytics/suites/bazel-bazel/tests/018a9945-300c-7030-a16b-dff6d58298a8?branch=master

BAZELCI_TASK=rbe_ubuntu2004
TEST_TARGET=//src/test/py/bazel:bazel_external_repository_test
TEST_NAME=testNewHttpTarArchiveWithSymlinks

bazel test //src/test/py/bazel:bazel_external_repository_test --test_filter=testNewHttpTarArchiveWithSymlinks

Logs:

Traceback (most recent call last):
  File "/b/f/w/bazel-out/k8-fastbuild/bin/src/test/py/bazel/bazel_external_repository_test.runfiles/_main/src/test/py/bazel/bazel_external_repository_test.py", line 162, in testNewHttpTarArchiveWithSymlinks
    self.RunBazel([
  File "/b/f/w/bazel-out/k8-fastbuild/bin/src/test/py/bazel/bazel_external_repository_test.runfiles/_main/src/test/py/bazel/test_base.py", line 424, in RunBazel
    return self.RunProgram(
  File "/b/f/w/bazel-out/k8-fastbuild/bin/src/test/py/bazel/bazel_external_repository_test.runfiles/_main/src/test/py/bazel/test_base.py", line 580, in RunProgram
    self.AssertExitCode(exit_code, 0, stderr_lines, stdout_lines)
  File "/b/f/w/bazel-out/k8-fastbuild/bin/src/test/py/bazel/bazel_external_repository_test.runfiles/_main/src/test/py/bazel/test_base.py", line 191, in AssertExitCode
    self._AssertExitCodeIs(actual_exit_code, lambda x: x == expected_exit_code,
  File "/b/f/w/bazel-out/k8-fastbuild/bin/src/test/py/bazel/bazel_external_repository_test.runfiles/_main/src/test/py/bazel/test_base.py", line 176, in _AssertExitCodeIs
    self.fail('\n'.join([
AssertionError: Bazel exited with 48 (expected 0), stderr:

CC Greenteam @meteorcloudy

@sgowroji sgowroji added type: bug breakage team-ExternalDeps External dependency handling, remote repositiories, WORKSPACE file. flaky test untriaged labels Apr 15, 2024
@meteorcloudy meteorcloudy added P2 We'll consider working on this in future. (Assignee optional) and removed untriaged labels Apr 16, 2024
@meteorcloudy
Copy link
Member

This flaky failure actually doesn't happen very often, so not prioritizing it as P1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breakage flaky test P2 We'll consider working on this in future. (Assignee optional) team-ExternalDeps External dependency handling, remote repositiories, WORKSPACE file. type: bug
Projects
None yet
Development

No branches or pull requests

2 participants