Speed up the functional tests #297
Draft
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
darosior
force-pushed
the
tests_speedup
branch
from
29aeaf5
to
cac568e
Compare
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.
Analog to #287, based on #292.
The main bottlenecks for the test framework currently are:
The former is limited by the Coordinator poll interval for signatures exchange and the latter by the bitcoind RPC poll interval for chainstate update. Reducing both drastically reduces the run time of the functional tests suite but reducing the bitcoind RPC poll interval currently is flaky on a race in the reorg tests, this is why it's still a draft.
On my machine this speeds up the tests from taking ~12min to ~6min (will edit shortly).