-
Notifications
You must be signed in to change notification settings - Fork 78
[Etcm 521] Fast sync integration tests #944
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
Conversation
src/main/scala/io/iohk/ethereum/blockchain/sync/fast/FastSync.scala
Outdated
Show resolved
Hide resolved
9f1e8ff to
bd77cd1
Compare
9c2080c to
39ab6b1
Compare
- Apply fix for branch resolving not being started
39ab6b1 to
9ae6a32
Compare
jvdp
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.
LGTM 👍
Did raise some questions, and I think more comments/descriptions would be nice to have for FakePeer DSL.
| } | ||
| } | ||
|
|
||
| it should "switch to regular sync once `safeDownloadTarget` is reached" in customTestCaseResourceM( |
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.
Where do you assert that regular sync was initiated?
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.
the CommonFakePeer#waitForFastSyncFinish() helper method checks for the completion of Fastsync. More specific assertion can be made possible by intercepting the logs only. Maybe something to improve in another ticket to add support for intercepting logs in tests.
Description
This PR adds integration tests for the newly introduced fast sync improvements (Concurrent download of headers)
Important Changes Introduced
Minor fixes were applied to the original implementation of
FastSync, which prevented the branch resolution from being completed properly.Testing
Run the tests and look through the logs for branch resolution when a malicious master peer is found.