jerrytesting
jerrytesting
In the latest commit version: 05a49e0, one assertion failed: src/uv_truncate.c:58: void uvTruncateWorkCb(uv_work_t *): Assertion `i < n_segments'. Attached is the log file [n_segments-assertion-failure.log](https://github.com/jerrytesting/c-raft_bugLogs/blob/main/n_segments-assertion-failure.log). Hope it could help you debug.
when one killed node rejoins the cluster, one memory leak happens. The following is the sanitizer report: ``` 1: raft_start(): io: load closed segment 0000000000000138-0000000000000201: entries batch 5 starting at...
We found one inconsistency issue about not read committed. Here is the full log: [https://github.com/jerrytesting/braft-inconsistency/tree/main/20230326T082122.918Z](https://github.com/jerrytesting/braft-inconsistency/tree/main/20230326T082122.918Z), and hope it could help figure out the issue.
We found one memory leak bug while running atomic-server. Here is the bug report from the sanitizer: ``` Direct leak of 56 byte(s) in 1 object(s) allocated from: -- #0...
In the latest commit version: 05a49e0, one assertion failed: src/uv_truncate.c:58: void uvTruncateWorkCb(uv_work_t *): Assertion `i < n_segments'. Attached is the log file [n_segments-assertion-failure.log](https://github.com/jerrytesting/c-raft_bugLogs/blob/main/n_segments-assertion-failure.log). Hope it could help you debug.
We found one consistency issue about not read uncomitted in the latest raft version. Here is the bug log: [https://github.com/jerrytesting/inconsistent-bugs-canonical-raft/tree/main/not_read_uncommitted](https://github.com/jerrytesting/inconsistent-bugs-canonical-raft/tree/main/not_read_uncommitted) and hope it could help you debug.
Hello, we found one memory issue about DEADLYSIGNAL reported by the AddressSanitizer in version 0.14.0. The following is the bug report: ``` LIBRAFT 1679628518277105579 src/replication.c:1234 restored snapshot with last index...
While running raft-v0.17.1, Jepsen harness reports the `for Jepsen: extra online spare` error. Your Jepsen harness configures the keyword `for jepsen` as `assertion-pattern`, so I think this is the abnormal...