qa tests: increase snap-download test deadline #10387
Merged
Conversation
This file contains 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
On the mainnet, the snap-download process has shown significantly higher completion times. On release/2.60, it typically takes around 2 hours. However, for Erigon mainnet (v3), which requires downloading numerous snapshots, 8 hours should be sufficient. Unfortunately, this is not the case; the test reaches only about 95% completion within 8 hours. The number of peers remains consistent (a few hundred).
Therefore, this PR proposes to increase the deadline, at least temporarily. Total test times are recorded as usual in MongoDB for historical comparison. By extending the deadline, we allow Erigon to complete the download process, which helps us identify if there are other underlying issues.