This repository has been archived by the owner on Jan 11, 2024. It is now read-only.
FM-363: Block sync test #459
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
aakoshh
force-pushed
the
fm-363-state-sync-test
branch
from
267a323 to
1f158ac
Compare
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.
Part of consensus-shipyard/ipc#178
This PR sets up a full node to follow the default one, and asserts that blocks are being synced starting from genesis. It doesn't use state sync yet.
The fact that this works despite the test configuring
FM_DB_HIST_SIZE=100is because the retain_height is still set to 0, until snapshots are implemented. That would be the next step, to sync from a snapshot, which will require further configuration.