Flaky-test: ClientDeduplicationFailureTest.testClientDeduplicationCorrectnessWithFailure
Open
area/test
help wanted
lifecycle/stale
Stale
type/flaky-tests
- Dominant language
- Java
- Stars
- 15.3k
- Forks
- 3.8k
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 160
Description
ClientDeduplicationFailureTest.testClientDeduplicationCorrectnessWithFailure is flaky. It fails sporadically. It was disabled in https://github.com/apache/pulsar/pull/14509 because it was leading to out of memory errors. Ideally, we'll find a way to re-enable it without causing OOM.
Contributor guide
Research direction
Start with ClientDeduplicationFailureTest.testClientDeduplicationCorrectnessWithFailure and review why it was disabled in pull request 14509. Investigate the sporadic failure and out-of-memory errors; done means the test can be re-enabled without causing OOMs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- distributed-systems, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100