[Flaky Test][TeZ] WriteBufferManagerTest.testWriteNormal
- Dominant language
- Java
- Stars
- 454
- Forks
- 172
- Avg merge
- 5d 17h
- Merged PRs (30d)
- 5
Description
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
### Search before asking
- [X] I have searched in the [issues](https://github.com/apache/incubator-uniffle/issues?q=is%3Aissue) and found no similar issues.
### Describe the flaky test
WriteBufferManagerTest.testWriteNormal
### Actions URL
https://github.com/apache/incubator-uniffle/actions/runs/6704550390/job/18217184953
### Are you willing to submit PR?
- [ ] Yes I am willing to submit a PR!
Contributor guide
Research direction
Start with WriteBufferManagerTest.testWriteNormal and review the linked GitHub Actions run for the failure details. Reproduce the test locally if possible, then trace the reported failure to determine what makes it flaky. Done means the test passes reliably without masking the underlying behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100