-
Notifications
You must be signed in to change notification settings - Fork 10
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
IF: Test: Increase allowed unlinkable block exceptions during syncing #82
Conversation
Issue #69 mentioned |
I thought I had reported that number incorrectly and it was actually 129. I looked again. The first failure was 219 and the second was 129. So, 500 might be a better option. |
tests/nodeos_startup_catchup.py
Outdated
# See https://github.com/AntelopeIO/spring/issues/81 for fix to reduce the number of expected unlinkable blocks | ||
# Test verifies LIB is advancing, check to see that not too many unlinkable block exceptions are generated | ||
# while syncing up to head. | ||
if contents.count("3030001 unlinkable_block_exception: Unlinkable block") > 500: |
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 you log the count too so we know right away the number causing the violation.
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.
Added print
Note:start |
For this issue, just want to make the test more reliable and less sensitive to the number of unlinkable blocks that occurred during the test.
A separate issue #81 was created as a low-priority optimization to reduce the likelihood of these unlinkable blocks occurring during lib catchup syncing.
Resolves #69