test: add trim_headers functional test #1249
Closed
Conversation
This file contains hidden or 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
Contributor
|
I think the key to reproducing #1241 is prune, so you'd need at least 550MB worth of blocks to trigger it |
delta1
force-pushed
the
trim-headers-test
branch
from
262dcf2 to
8bf5123
Compare
Member
Author
|
Updated the test and description |
delta1
force-pushed
the
trim-headers-test
branch
from
f59686b to
5dcde52
Compare
Member
Author
|
rebased on master |
delta1
force-pushed
the
trim-headers-test
branch
from
5dcde52 to
c6c853e
Compare
Member
Author
|
was included in #1270 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
fixes #1242
This test is based on
feature_blocksign.py. It runs 1 block-signing nodes and 2 syncing nodes withtrim_headers=1, 1 of which also has-prune=550.This reproduces the crash in #1241