jihuayu opened a new issue, #3515:
URL: https://github.com/apache/kvrocks/issues/3515
Several recent `kvrocks.yaml` CI runs failed in replication tests that
simulate broken or slow replication links.
The most frequent failure is `TestSlaveLostMaster`:
```
--- FAIL: TestSlaveLostMaster
client.go:147: forward tcp stream failed, err: read tcp 127.0.0.1:...:
read: connection reset by peer
FAIL github.com/apache/kvrocks/tests/gocase/integration/replication
```
Examples:
- https://github.com/apache/kvrocks/actions/runs/27181757902
- https://github.com/apache/kvrocks/actions/runs/27136241761
- https://github.com/apache/kvrocks/actions/runs/27135463274
- https://github.com/apache/kvrocks/actions/runs/26640257024
- https://github.com/apache/kvrocks/actions/runs/26447014065
This does not seem related to the PR contents. It has appeared across
unrelated stream/cf/hash/dependency changes and across different CI matrix
entries, especially macOS arm64, but not only there.
The failure appears to come from `util.SimpleTCPProxy` calling `t.Fatalf`
from the proxy forwarding goroutine when the TCP connection is reset. In
`TestSlaveLostMaster`, the test intentionally breaks the proxy connection to
simulate a lost master, so a connection reset during that phase may be expected
and should probably not fail the test directly.
Proxy-based tests worth auditing:
- `TestSlaveLostMaster`
- `TestSlowConsumerBug`
- `TestSlowConsumerBlocksIndefinitely`
### Execute the necessary steps
- Investigate the reasons for failure
- Confirm the purpose of the test cases
- Propose solutions (communication is very important)
- Complete the code implementation
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
