-
Notifications
You must be signed in to change notification settings - Fork 217
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Towards trace validation of real CCF nodes #5794
Comments
For comparison, this is a trace extract from the schema test, a one-node end to end test:
|
Note from discussion with @lemmy and @eddyashton: We can simplify the trace spec if we log state before and after actions such as |
The JSON key in the "after" action should not be named |
Summarising some more issues spotted in discussion with @achamayou:
|
Second one has a repro in #5798 |
Superseded by #5822. |
This is taking a step back from #5769, to document the existing gap between the raft driver, and actual nodes, with the goal of closing it.
As of af21407, using
jq .msg -c
to remove the less important fields such as timestamps etc.A three node network startup, in the driver
There are some discrepancies here with the way a CCF network starts, as outlined in the documentation.
replicate
(whenLeader
) orrecv_append_entries
(whenBackup
).Start
node will instead become leader without an election. Since it has no configuration, it wouldn't know who to ask for votes.The text was updated successfully, but these errors were encountered: