-
Notifications
You must be signed in to change notification settings - Fork 787
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Fix node.pruning_*
unit tests
#3687
Conversation
ASSERT_TRUE (node1.ledger.block_or_pruned_exists (nano::dev::genesis->hash ())); | ||
ASSERT_TRUE (node1.ledger.block_or_pruned_exists (send1->hash ())); // true for pruned | ||
ASSERT_TRUE (node1.ledger.block_or_pruned_exists (send1->hash ())); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wouldn't remove this comment as it is there to facilitate debugging. If you have more info to add about the tests please do so.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I did add some relevant comments at the beginning of the tests.
@@ -4300,161 +4300,176 @@ TEST (rep_crawler, local) | |||
|
|||
TEST (node, pruning_automatic) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we add a comment describing the intention of this unit test?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will do, thanks
90826c4
to
9ecd690
Compare
One more batch of fixes, put them in the same PR due to the tests being fairly similar to one another.
One of them (
node.pruning_age
) just very recently was disabled in #3629, so linking the respective issue (#3641) to this PR.