This repository has been archived by the owner on Aug 2, 2022. It is now read-only.
CFD pruning integration test #9072
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…nto cfd-integration-test # Conflicts: # tests/eosio_blocklog_prune_test.py
heifner
approved these changes
May 11, 2020
heifner
approved these changes
May 11, 2020
heifner
approved these changes
May 11, 2020
|
Very nice work Huang-Ming. Thanks |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Change Description
This test creates a producer node and 2 verification nodes.
The producer node is configured with state history plugin.
A transaction with context free data is pushed to the producer node.
Both validation nodes are stop before the context free data has been pushed.
Next, it uses eosio-blocklog to prune the transaction with context free
data, restart the producer node and check if the context free data in the block
log has actually been pruned.
Afterwords, both validation nodes are restarted and checks whether the light validation
node keeps syncing after the block with context free data while the full validation node
stops syncing right at the block.
Consensus Changes
API Changes
Documentation Additions