Reenable tests for gRPC UDS proxy
- Dominant language
- Java
- Stars
- 25.8k
- Forks
- 4.6k
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 72
Description
https://cs.opensource.google/bazel/bazel/+/master:src/test/shell/bazel/remote/remote_execution_test.sh;l=161;drc=b303cd128d9f1d913749927f4a1cd942b10b1ae2
https://cs.opensource.google/bazel/bazel/+/master:src/test/shell/bazel/remote/remote_execution_test.sh;l=200;drc=b303cd128d9f1d913749927f4a1cd942b10b1ae2
They were disabled due to flakiness in 8e3c0df. As a consequence, we introduced an undetected regression in 5.3 (#16171).
Contributor guide
Research direction
Start with src/test/shell/bazel/remote/remote_execution_test.sh at the referenced lines and review commit 8e3c0df, which disabled the tests because of flakiness. Compare the tests with regression #16171 and run the relevant remote execution tests; done means the gRPC UDS proxy tests are reenabled without flakiness and cover the regression.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- grpc, shell
- Domain
- build-system, testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100