-
Notifications
You must be signed in to change notification settings - Fork 2.1k
make timelord/test_new_peak.py a bit more robust #20271
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
base: main
Are you sure you want to change the base?
Conversation
Pull Request Test Coverage Report for Build 19477990032Details
💛 - Coveralls |
|
so this was failing whenever the blocks turned out to be overflow ? i think it would be better to check if the block is overflow or not and check the relevant list |
Yes. I suspect that with the new chains I generated, some of these blocks happened to be overflow blocks, by chance. |
871d43f to
3e49161
Compare
|
wjblanke
left a comment
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.
aok
Purpose:
This test is ensuring unfinished blocks ended up accepted by the timelord. However, the timelord sometimes record unfinished blocks in the
overflowslist.This makes the test pick either of the lists, and therefore makes it more robust as we add new test chains. We'll add additional test chains for the 3.0 hard fork.