jerrytesting

Hi, I uploaded the full logs with our Jepsen++ tool: [https://github.com/jerrytesting/Canonical-raft-bug-logs/](https://github.com/jerrytesting/Canonical-raft-bug-logs/). You could find `Assertion `i < n_segments'` failed in the logs of node n1, n3, and n5.

Besides this bug, this log contains another assertion failure: In the logs of node n1, there is another assertion failed: `Assertion `r->state == RAFT_FOLLOWER || r->state == RAFT_CANDIDATE' failed`.

Besides, we also found one consistency issue about not read committed: [https://github.com/jerrytesting/inconsistent-bugs-canonical-raft/tree/main/not_read_committed](https://github.com/jerrytesting/inconsistent-bugs-canonical-raft/tree/main/not_read_committed)

Sorry that our Jepsen setup is not open-sourced now but it will be soon. Currently, I can only give you enough bug reports to help you figure out the issues.

Yes, included the assertion checker and reported two assertion failures in ISSUE-291. We are still running to see whether we can capture other issues.

Hey, we run in v0.14.0. I think it should not be the setup issue as we use your Jepsen harness. Will upload the full logs soon (some logs are very...

Yeah, there was one bug in our tool that the stop-partition nemesis was not invoked and so not executed. Thanks for finding this bug in our tool. However, the other...

Hey, here is the node log and data: [https://github.com/jerrytesting/dqlite-memoryIssues/tree/main/DEADLYSIGNAL](https://github.com/jerrytesting/dqlite-memoryIssues/tree/main/DEADLYSIGNAL)