[Failing Test]: TestAutomatedExpansionService in Go SDK is flaky on precommits
- Dominant language
- Java
- Stars
- 8.7k
- Forks
- 4.7k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 196
Description
### What happened?
Flaky test in GO SDK
=== RUN TestAutomatedExpansionService
expansion_test.go:47: failed to start expansion service JAR, got context deadline exceeded
--- FAIL: TestAutomatedExpansionService (15.01s)
Links:
1. https://ci-beam.apache.org/job/beam_PreCommit_Go_Commit/13386/console
2. https://ci-beam.apache.org/job/beam_PreCommit_GoPortable_Commit/4771/
### Issue Failure
Failure: Test is flaky
### Issue Priority
Priority: 2 (backlog / disabled test but we think the product is healthy)
### Issue Components
- [ ] Component: Python SDK
- [ ] Component: Java SDK
- [X] Component: Go SDK
- [ ] Component: Typescript SDK
- [ ] Component: IO connector
- [ ] Component: Beam examples
- [ ] Component: Beam playground
- [ ] Component: Beam katas
- [ ] Component: Website
- [ ] Component: Spark Runner
- [ ] Component: Flink Runner
- [ ] Component: Samza Runner
- [ ] Component: Twister2 Runner
- [ ] Component: Hazelcast Jet Runner
- [ ] Component: Google Cloud Dataflow Runner
Contributor guide
Research direction
Start with expansion_test.go at line 47 and reproduce TestAutomatedExpansionService using the linked Go precommit job logs. Investigate why the expansion service JAR exceeds the 15-second startup deadline; done means the test starts reliably and the Go precommit tests pass without flaking.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100