Bazel CI Flaky src.test.shell.bazel.bazel_test_test test_xml_is_present_when_timingout
Open
flaky test
team-Core
type: bug
untriaged
- Dominant language
- Java
- Stars
- 25.8k
- Forks
- 4.6k
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 72
Description
https://buildkite.com/organizations/bazel/analytics/suites/bazel-bazel/tests/01884414-2fe2-727d-8d11-680c795284e3?branch=master
Platform : MACOS
Logs:
```
//src/test/shell/bazel:bazel_test_test FLAKY,
```
CC Greenteam @Wyverald
Contributor guide
Research direction
Start by opening the linked Buildkite analytics record and examining the macOS logs for //src/test/shell/bazel:bazel_test_test, focusing on the test_xml_is_present_when_timingout failure. Done means the timeout behavior is reliable and the target no longer reports FLAKY.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system, ci-cd, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100