Closed hansieodendaal closed 3 months ago
3 files 120 suites 43m 57s :stopwatch: 1 279 tests 1 279 :white_check_mark: 0 :zzz: 0 :x: 3 829 runs 3 829 :white_check_mark: 0 :zzz: 0 :x:
Results for commit 25d4b933.
2 files 11 suites 25m 3s :stopwatch: 33 tests 30 :white_check_mark: 0 :zzz: 3 :x: 37 runs 32 :white_check_mark: 0 :zzz: 5 :x:
For more details on these failures, see this check.
Results for commit 25d4b933.
Description
Adjusted block sync timeouts to enable block sync over tor when we have many full blocks. Previous values were unrealistic and unfeasible. This PR provides feasible default values for full blocks sync over tor for a fresh base node.
Motivation and Context
A recent stress test on
esemeralda
provided a blockchain with many full blocks. Performing a fresh base node block sync over tor in a controlled environment proved impossible due to inherent network latencies. Although there may be a fix to improve the tor latencies with full blocks sync, it is not yet available.How Has This Been Tested?
Many system-level tests.
What process can a PR reviewer use to test or verify this change?
Code review and system-level tests.
Breaking Changes