Bazel CI flaky test failure com.google.devtools.build.lib.server.GrpcServerTest testInterruptStream
- 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/01880a58-5233-71f5-bd0f-793736b8bac0?branch=master#flaky
Found in list of Post-submit CI Builds : [https://buildkite.com/organizations/bazel/analytics/suites/bazel-bazel/tests/01880a58-5233-71f5-bd0f-793736b8bac0?branch=master#failed](https://buildkite.com/organizations/bazel/analytics/suites/bazel-bazel/tests/01880a39-672a-75de-b7f4-e14060369f53?branch=master#failed)
Logs:
```
FLAKY: com.google.devtools.build.lib.server.GrpcServerTest testInterruptStream
```
CC Greenteam [@fweikert](https://github.com/fweikert)
Contributor guide
Research direction
Start with the linked Buildkite flaky-test report and the com.google.devtools.build.lib.server.GrpcServerTest testInterruptStream entry point. Reproduce or inspect the failure logs, then identify and stabilize the flaky test; done means the test no longer intermittently fails in post-submit CI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system, ci-cd, testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100