Flaky test in TLS replication
- Dominant language
- C++
- Stars
- 4.4k
- Forks
- 658
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 10
Description
### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/kvrocks/issues) and found no similar issues.
### Version
unstable
### Minimal reproduce step
https://github.com/apache/kvrocks/actions/runs/6159066781/job/16713576822
https://github.com/apache/kvrocks/actions/runs/6180335719/job/16776798127
https://github.com/apache/kvrocks/actions/runs/6155474342/job/16702713002
### What did you expect to see?
-
### What did you see instead?
-
### Anything Else?
_No response_
### Are you willing to submit a PR?
- [ ] I'm willing to submit a PR!
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the three linked GitHub Actions job logs and compare the failures in the TLS replication test. Trace the test and its replication entry points to identify the intermittent condition, then verify that the test completes reliably in repeated CI runs without TLS replication failures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- databases, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100